Hi @orencivier
Thank you very much for your reply. I have just tried Neurodesktop, excellent container! I have a few questions regarding this desktop.
I successfully launched the container on the server, and I can access to it via my PC’s browser, however, the IP address is fixed to the server(the machine which runs the container), I wonder if other users on the server using the same images, could they create containers with different port number and access they own environment, would this work? In other words, I just hope everyone on the server can use Neurodesk without bothering each other.
If I understand correctly, Neurodesk will pull the corresponding images when first time starting it, however, I got stuck there because of the firewall, my working environment uses a proxy server, how shall I set up the proxy address inside the Neurodesk?
For instance, when I pull an image inside Neurodesk by:
singularity pull tensorflow.sif docker://tensorflow/tensorflow:latest
The error message I got:
FATAL: While making image from oci registry: error fetching image to cache: failed to get checksum for docker://tensorflow/tensorflow:latest: pinging container registry registry-1.docker.io: Get "http://registry-1.docker.io/v2/": dial tcp 54.236.165.68:80: i/o timeout
As far as I know, this issue is mainly caused by the network settings, which happened when pulling images from the Docker hub on my server. It was resolved by configuring the proxy address and port in the proxy file.
/etc/systemd/system/docker.service.d/http-proxy.conf
Inside of Neurodesk, where can I set up the proxy setting so that I can download images?
The following does not work:
export http_proxy=http://<ip>:<port>
export https_proxy=http://<ip>:<port>