I just want to upgrade my docker-compose version,because local machine version is different from Linux server(Production),so every deploy i must manual update the xxx.yml (such as update "port" to port ,add "version" tag),Lasterday i use below code to upgrade my docker-compose,unfortunately,docker.service is shutdown,and all container has been stoped and removed
the old docker has been setted on /mnt/data/dockerwhen i update /etc/docker/daemon.json reset "data-root" on old folder"/mnt/data/docker" ,systemctl restart docker command has been failed,,so i remove daemon.json again,a few moments later, docker.service is restarted...
Question1: because /mnt/data/docker is not a empty folder so docker.service start failed?
Question2: may i remove "/mnt/data/docker" folder? is it affect running container?
Description
I just want to upgrade my docker-compose version,because local machine version is different from Linux server(Production),so every deploy i must manual update the xxx.yml (such as update "port" to port ,add "version" tag),Lasterday i use below code to upgrade my docker-compose,unfortunately,docker.service is shutdown,and all container has been stoped and removed
so i just reinstall docker.service and redeploy all services to maintain service worked for user.
after this all, docker ""data-root": has default setted on little space disk,because i removed daemon.json
Question1: because /mnt/data/docker is not a empty folder so docker.service start failed? Question2: may i remove "/mnt/data/docker" folder? is it affect running container?
Reproduce
yum update yum install docker-compose-plugin yum remove docker yum install docker systemctl restart docker
Expected behavior
No response
docker version
docker info
Diagnostics ID
i don't know...
Additional Info
No response