Skip to content





The installation records on Rocky Server is here.

Directly type docker in the terminal,

$ docker

Command 'docker' not found, but can be installed with:

sudo snap install docker     # version 19.03.11, or
sudo apt  install

See 'snap info docker' for additional versions.

then run

sudo apt install

Without permission, it will report the following message

$ docker version
 Version:           19.03.6
 API version:       1.40
 Go version:        go1.12.17
 Git commit:        369ce74a3c
 Built:             Fri Feb 28 23:45:43 2020
 OS/Arch:           linux/amd64
 Experimental:      false
Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.40/version: dial unix /var/run/docker.sock: connect: permission denied

To avoid permission issue,

sudo usermod -aG docker $USER
# re-evaluate the group membership
newgrp docker

change the root folder

to save space, I want to change the image installation directory:

$ sudo vi /etc/docker/daemon.json
  "data-root": "/new/path/to/docker-data"
$ sudo systemctl daemon-reload
$ sudo systemctl restart docker

where the official explanation is that

  • data-root is the path where persisted data such as images, volumes, and cluster state are stored. The default value is /var/lib/docker

we can validate it with the hello-world image,

$ docker image pull hello-world
# or docker image pull library/hello-world
$ docker image ls
REPOSITORY          TAG                 IMAGE ID            CREATED             SIZE
hello-world         latest              d1165f221234        7 weeks ago         13.3kB
$ docker image inspect d1165
        "Id": "sha256:d1165f2212346b2bab48cb01c1e39ee8ad1be46b87873d9ca7a4e434980a7726",
        "RepoTags": [
        "GraphDriver": {
            "Data": {
                "MergedDir": "/media/weiya/PSSD/Programs/docker/overlay2/511d95f2c0f646ed080c006f99f8f738f967231d33aaa36a98e3e67109eb09be/merged",
                "UpperDir": "/media/weiya/PSSD/Programs/docker/overlay2/511d95f2c0f646ed080c006f99f8f738f967231d33aaa36a98e3e67109eb09be/diff",
                "WorkDir": "/media/weiya/PSSD/Programs/docker/overlay2/511d95f2c0f646ed080c006f99f8f738f967231d33aaa36a98e3e67109eb09be/work"



Post on: 2023-01-07 19:52:47 -0500

act, which is based on docker, supports to run GitHub actions locally.

Installation of act

  1. Download the binary package
  2. /usr/local/bin$ sudo ln -s /media/weiya/PSSD/Programs/act-0.2.35/act .

If the container still exists, we can also open a terminal to access it like a server,

~$ docker container ls
CONTAINER ID   IMAGE                           COMMAND               CREATED        STATUS        PORTS     NAMES
e801ec7aed7f   catthehacker/ubuntu:act-20.04   "tail -f /dev/null"   23 hours ago   Up 23 hours             act-CI-Julia-1-8--ubuntu-20-04
~$ docker exec -it e801 bash



The images are hosted on Docker Official Images: r-base.

Without pulling,

docker pull r-base:4.1.0

we can directly run the following code,

docker run -it r-base:4.1.0

then the R session would appear. We can install packages as usual, such as

> install.packages("dplyr")

but note that the modification would discard after quitting. So it is necessary to save the changes (refer to How to Commit Changes to a Docker Image with Examples) via

$ docker commit container-ID new-image-name

Next time, we can run with the installed packages,

$ docker run -it new-image-name

If we want to plot, then it is necessary to forward X11, see Alternatives to ssh X11-forwarding for Docker containers for more details. Or as @edd suggested in Enable plotting for r-base container via X-Forwarding, a better one might be to use a container with RStudio Server.


XAMPP is a free and open-source cross-platform (X) web server solution stack package developed by Apache Friends, consisting mainly of the Apache HTTP Server (A), MariaDB database (M) (formerly MySQL), and interpreters for scripts written in the PHP (P) and Perl (P) programming languages.

Here is a great docker image!

Start via

#$ docker pull tomsik68/xampp
$ docker run --name myXAMPP -p 41061:22 -p 41062:80 -d -v ~/my_web_pages:/www tomsik68/xampp:8


  • docker run and docker container run are exactly the same
  • since docker run will automatically download the image if no installed, then docker pull is unnecessary. 🔗
  • -v /HOST-DIR:/CONTAINER-DIR creates a bind mount.
  • -p hostPort:containerPort publishes the container’s port to the host.
  • -d runs the container in the background and print the new container ID.
  • 🔑 More details can be checked via man docker-run.

Then we can see the container via

$ docker container ls
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS                                                    NAMES
43e5a49cbfd5        tomsik68/xampp      "sh /"    18 seconds ago      Up 17 seconds       3306/tcp,>22/tcp,>80/tcp   myXAMPP

Stop via

#$ docker container stop/kill [containerID]
$ docker stop/kill [containerID]
# then
$ docker stop 43e5
$ docker container ls
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES


  • similarly, docker container stop/kill can be abbreviated as docker stop/kill
  • kill 向容器里面的主进程发出 SIGKILL 信号,而 stop 发出 SIGTERM 信号,然后过一段时间再发出 SIGKILL 信号。两者差异是,应用程序收到 SIGTERM 信号后,可以自行进行收尾清理工作,但也可以不理会这个信号。如果收到 SIGKILL 信号,就会强行立即终止,那些正在进行的操作会全部丢失。🔗
  • containerID 无需写全,只要能区分即可
  • since we have specified the name via --name myXAMPP, we can replace the containerID with such name.

Restart via

# find the container ID
$ docker container ls -a
$ docker container start [containerID]/[containerNAME]


  • docker container ls only shows the running ones, but -a will show all containers. More details can be found in man docker-container-ls

Establish a ssh connection,

$ ssh root@ -p 41061

it sounds like the port-forwarding if we view the container as another linux machine.


Both default username and password are root.

Alternatively, we can get a shell terminal insider the container, just like ssh,

$ docker exec -it myXAMPP bash


  • -t allocates a pseudo-TTY.
  • -i keeps STDIN open even if not attached.
  • docker [container] exec 用于进入一个正在运行的 container. 如果 docker run 命令运行容器时,没有使用 -it,则需要这个命令进入容器。🔗

If we are inside the container, we can export the path to use the commands provided by XAMPP,

# inside docker container
export PATH=/opt/lampp/bin:$PATH
# or add it to `.bashrc` of the container

If we modified the configuration of XAMPP, we need to restart the Apache server via

docker exec myXAMPP /opt/lampp/lampp restart

Python (for a non-internet env)

First of all, write a dockerfile

cat Dockerfile
FROM python:3.7
RUN pip install jieba

then build it with

$ docker image build -t py37jieba:0.0.1 .

and test it locally with

$ docker run -it py37jieba:0.0.1 
Python 3.7.10 (default, May 12 2021, 16:05:48) 
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import jieba
>>> jieba.cut("他来到了网易杭研大厦")
<generator object Tokenizer.cut at 0x7fda1c981bd0>
>>> print(", ".join(jieba.cut("他来到了网易杭研大厦")))
Building prefix dict from the default dictionary ...
Dumping model to file cache /tmp/jieba.cache
Loading model cost 0.924 seconds.
Prefix dict has been built successfully.
他, 来到, 了, 网易, 杭研, 大厦

save the image with

$ docker save py37jieba:0.0.1 | gzip > py37jieba-0.0.1.tar.gz

refer to hubutui/docker-for-env-without-internet-access

We can also treat it as a new server visiting from bash,

docker run -it --rm -v /tmp:/root -w /root py37jieba:0.0.5 bash

and open another terminal via

docker exec -it <containerID> bash


no space left on device: unknown

$ docker system prune

refer to Docker error : no space left on device

ownership of generated files

The default ownership file is root, and fail to accessed.

We can specify the owner if necessary,

$ docker run -v $PWD:/root -w /root -u $UID:$UID -it py37jieba:0.0.5 bash

where the valid formats from man docker-run include

          --user [user | user:group | uid | uid:gid | user:gid | uid:group ]

but a direct username weiya throws,

docker: Error response from daemon: unable to find user weiya: no matching entries in passwd file.
ERRO[0000] error waiting for container: context canceled 

with a specific uid, the prompt displays

I have no name!@afea1a0b4bd7:/root$ echo "own by weiya" > test_ownship.txt

Test with 1000 and 1000:1000 respectively, the results are

-rw-r--r-- 1 weiya weiya        13 Jul 14 13:36 test_ownship2.txt
-rw-r--r-- 1 weiya root         13 Jul 14 12:04 test_ownship.txt

refer to Files created by Docker container are owned by root

Run in background

Suppose I want to run a script in the background, the classical way is

$ python &

But with docker, the correct way is to add option -d.

$ docker run -d 

refer to How to run a docker container in the background or detached mode in the terminal?

  • directly appending & did not work.
  • nohup docker ... & also failed


See SZmedinfo/issues/11 for some failed attempts

Another related task is to run the script in the background of docker, which can keep the container running forever,

RUN bash -c "sh & tail -F /dev/null"

refer to Run a background script inside a docker container

from time import sleep
f = open("test.txt", "w")

write out log file, do not use the abbreviated version, &> since it is only supported in bash, and instead write the full format

RUN sh -c 'python > out.log 2>&1'