Persistent storage: save your data outside the containerĬaution: avoid saving data inside the container, because this storage is not persistent and will be lost at next docker stop. on Ubuntu 16.04 (and later), it is absolutely necessary to enable PTRACE capabilities required by NoMachine, because they are not provided by the default docker AppArmor profile - hence the -cap-add=SYS_PTRACE parameter (see Build and Deploy NoMachine Desktops and Applications in Docker for Linux.memory and CPU quotas, CPU pinning), see Limit a container's resources for details the -cap-add option grants additional priviledges to the container and manages quotas (e.g.
#Nomachine client update
the -memory-reservation option specifies the soft limit on the memory use, an indication of intended memory usage rather than a maximum cap (the container is still allowed to use as much memory as it needs) note that this can be later changed using docker update.the -p option sets up port forwarding: contenerized SSH and NX servers use their standard ports, but non-standard ports are exposed outside the contained (here incremented by one) these exposed ports were defined in the Dockerfile.the -v option maps en external storage folder to the internal container folder, thus: -v /external/folder:/internal/folder.the -rm option will remove the docker image and other objects to release memory after the container is stopped (caution: potential data loss of the data stored inside the container).the -d option will run the container in the background (returning control to the shell at the cost of hiding errors messages displayed inside the container).if you don't have automated builds configured in Docker Hub, or if your have cancelled a build in Docker Hub, then you need to build the image locally (possibly cloning the GitHub repo first):ĭocker run -d -rm -p 4000:4000 -p 22:22 -name docker-nomachine-desktop -v /home/nomachine:/home/nomachine -memory-reservation 8G -cap-add=SYS_PTRACE mirekphd/docker-nomachine-desktop:latest.if you have linked GitHub with the Docker Hub, than create an automated build in the Docker Hub for this Docker image (see automated builds on Docker Hub), so that simply changing the Dockerfile in GitHub repo will automatically build and push the image to the Docker Hub,īuilding and tagging the Docker image locally.classic GUI-based IDEs (Spyder, P圜harm CE, and RStudio), designed for local use and thus requiring a graphical Desktop (here: Lubuntu/LXDE - a lightweight alternative to the standard Unity desktop), accessible inside the container through a desktop server (here: the NoMachine server, based on NX, a protocol superior to VNC).command-line tools (such as python3 / ipython, R), accessible via SSH clients or docker exec command,.A starter Python 3 and R environment for data science tasks performed on the server-side using a wide array of development tools for Python 3 and R:
0 kommentar(er)
