Please install docker by following the instructions in the: ref
sudo apt-get update sudo apt-get install apt-transport-https ca-certificates curl software-properties-common curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add - sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable" sudo apt-get update sudo apt-get install docker-ce
sudo docker run hello-world
you will see some results like
Hello from Docker! This message shows that your installation appears to be working correctly. ....
type the command:
$ docker run hello-world
you will see some results like
Hello from Docker! This message shows that your installation appears to be working correctly. ....
docker images
will list all the docker image in the current machine
You can search a docker image in the DockerHub(link:https://hub.docker.com/)
When you find a image you want to use, take the cselab_env image(link:https://hub.docker.com/r/ddnirvana/cselab_env/) as an example, you can pull the image by
docker pull ddnirvana/cselab_env:latest
here， ddnirvana/sharekernel_env is the name of the image, :latest is the tag of the image, which means the newest version of a image.
After the docker pull success, you can see the image has been downloaded in your local machine by docker images command
If you run a container without --rm options, actually you can re-enter the exitted container.
type
docker ps -a
and you will see some results like
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
8bec16084d97 test_commit:v1.0 "/bin/bash" 4 minutes ago Exited (0) 4 minutes ago quirky_goldberg
here, the 8bec16084d97 is your previous running container's id.
To re-enter this container, you should first start it, by
docker start 8bec16084d97
replace 8bec16084d97 to your container's id
and then, attach a terminal to the container, by
docker attach 8bec16084d97
replace 8bec16084d97 to your container's id too
Now, you will find you have re-enter the container and every things you have done are still here.
You can commit a container to a image anytime.
First, get the container id by
docker ps -a
and you will see some results like
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
8bec16084d97 test_commit:v1.0 "/bin/bash" 4 minutes ago Exited (0) 4 minutes ago quirky_goldberg
and then, commit a container to a image using the container's id
docker commit 8bec16084d97 test_commit:v1.0
here, 8bec16084d97 should be replaced by your container's id, and test_commit is the image name you want to give to your image, and v1.0 is the tag name you want to give to your image.
After that, you can see your new saved image by
docker images
1 . create a dir in the host machine, for example
mkdir -p /home/dd/courses/cse/lab_hostdir
2 . run a container
docker run -it --rm -v /home/dd/courses/cse/lab_hostdir:/home/devlop ddnirvana/cselab_env:latest /bin/bash
This command means we want to run a container from the image ddnirvana/cselab_env:latest. -it means attach the container's terminal to current terminal. --rm means remove the container when you exit it. -v /home/dd/courses/cse/lab_hostdir:/home/devlop means mount the host dir /home/dd/courses/cse/lab_hostdir to the container's dir /home/devlop.
Notes: everything in a docker container will be cleaned after you exit a container, so you need to store every usefull files in a mountted volume, in the above example, only files in /home/devlop in container will be persistent and every modification in these files will be persistent.
sudo docker run -it --rm --privileged --cap-add=ALL -v /home/cselabs/:/home/devlop ddnirvana/cselab_env:latest /bin/bash
Put the lab1's codes in container /home/devlop
Here, --privileged --cap-add=ALL will give the container ability to use fuse and do other privilege operations.