0
I'm running idoop/zentao:latest (zentao version: 11.6.1) docker container that includes Mysql server, apache server and web application.
When I try to connect to it using docker exec -it df4f599c64ec bash
command - it hangs.
When I try to stop it using docker stop df4f599c64ec
command - it hangs showing no errors.
When I try to commit it using docker commit df4f599c64ec zentao-25102019
command - it hangs.
When I connect to mysql inside of it - it connects to mysql's shell.
When I open hostaddress:81
which is my container's web application, it says, that
Can't create tmp directory, make sure the directory /opt/zbox/app/zentao/tmp/ exists and has permission to operate.
but before stop command it was working.
[root@ol7 ~]# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
df4f599c64ec idoop/zentao:latest "docker-entrypoint" 13 days ago Up 13 days (unhealthy) 0.0.0.0:81->80/tcp, 0.0.0.0:3307->3306/tcp zentao
I don't know, why this happened. Maybe because of lack of memory, because of 1.2Gb/6Gb of swap is used and only 143Mb/7.4Gb of RAM is free. Docker is running inside of proxmox VM. Host for docker is Oracle Linux 7.
How could I stop this container without loosing its changes? Will docker service restart help?
Updated: Checked my disk space:
[root@ol7 spacer]# df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 3.6G 0 3.6G 0% /dev
tmpfs 3.6G 0 3.6G 0% /dev/shm
tmpfs 3.6G 398M 3.2G 11% /run
tmpfs 3.6G 0 3.6G 0% /sys/fs/cgroup
/dev/sda1 54G 54G 15M 100% /
//192.168.1.21/public 932G 483G 450G 52% /mnt/super
overlay 54G 54G 15M 100% /var/lib/docker/overlay2/ceaff60a8dfee9d1129a927a0ae71cdb924222dd350527e89802a98fb2c4cb09/merged
shm 64M 0 64M 0% /var/lib/docker/containers/df4f599c64ec9d1bc8ddd0f03d13f797d7a41175e2bf16362a788ff0abacd333/mounts/shm
tmpfs 724M 0 724M 0% /run/user/1000
tmpfs 724M 0 724M 0% /run/user/0
It seems that I have no space required for docker to proceed.
1How could I stop this container without loosing its changes? A container is a throw-away thing. If you need to persist data in the container, you set up "volumes", so that the data exists independently of the container. If you need to make configuration changes, you create a derived image with a Dockerfile and
docker build
. Note that the doc says you should start a container with a volume (-v /data/zbox/:/opt/zbox/
), which by the way defines an/opt/zbox
. – xenoid – 2019-10-25T06:47:25.397