Merge 22.04 update (from previous sprint).

[bryanpaget]

This ticket is just to track the closing of StatCan/aaw#1784.

While the work has been done for updating the base images to Ubuntu 22.04, I am having difficulty building the images.

PR to merge 22.04 upgrade: #498

August 23 2023 Update

• The Remote Desktop image has been update to 22.04 but new errors have appeared that make the work incomplete.

1. R seems to function correctly and it's even running R 4.3.1! But I can't install any packages.
2. A "null" error upon opening rstudio-desktop

September 13 Update

I've kept the Ubuntu Desktop image back, the ticket to merge the downgrade is here and should be merged after the 22.04 upgrade PR.

• Downgrade remote desktop #519

[bryanpaget]

Blocked by #502

[bryanpaget]

Two new issues have emerged:

1. R seems to function correctly and it's even running R 4.3.1! But I can't install any packages. Fix inability to install R packages in the Remote Desktop image. #512
2. A "null" error upon opening rstudio-desktop. Fix "Null" error for new rstudio-desktop sessions. #513

[bryanpaget]

While testing the newly minted images I've discovered we can't import torch on the JupyterLab-Pytorch image.

• Unable to import torch on pytorch image. #514

[bryanpaget]

The "null" error on the remote-desktop image is still active.

I have opened a ticket on rstudio's Github repo:

rstudio/rstudio#13553

[bryanpaget]

The "null" error is most likely caused by an incompatibility between the chrome/electron wrapper around rstudio-desktop and kubernetes as described in the following bug report:

• ☸️ Can not run in Kubernetes? jlandure/alpine-chrome#109

[bryanpaget]

I tried downgrading the remote-desktop image so we can use an older version of rstudio-desktop and rstudio-server (since rstudio-server is installed in the base image) but that seems to cause problems for pspp and qgis.

[bryanpaget]

Since it seems like we can't update the remote-desktop image without breaking rstudio-desktop, I suggest the following path:

1. Revert the remote-destkop image to its previous working state and freeze it, i.e. put it on maintenence mode until 2.
2. Deprecate the remote-desktop image in favor of JupyterLab. I personally am in favour of this since the remote-desktop image is holding us back with its technical debt.