Forwarded to devs Docker extension issue - docker daemon running continuously, even after uninstall

[trialotto]

TITLE:

Docker extension issue - docker daemon running continuously, even after uninstall​

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:

Product version: Plesk Onyx 17.8.11 Update #70
Update date: 2019/10/09 02:43
Build date: 2019/10/03 04:49
OS version: Ubuntu 18.04
Revision: dace57d4eda000639cf29e8db0a5e38ae84b76e4
Architecture: 64-bit
Wrapper version: 1.2

Also appliers for other Ubuntu and Plesk releases - did not check Obsidian.​

PROBLEM DESCRIPTION:

Installing docker extension results in a running docker daemon.

ISSUE 1 : The docker daemon uses memory, even if no container is present.

ISSUE 2 : Docker daemon keeps running, even after deletion of the extension!

SUMMARY : memory overusage - there is no need for that!

ISSUE 3 - Deletion : after uninstalling the docker extension, the packages

- docker-ce
- docker-ce-cli
- containerd.io

are left behind : they have not been removed.​

STEPS TO REPRODUCE:

STR - ISSUE 1 :
1 - Install Docker extension
2 - run command : docker ps -a
3 - result is a table without containers - as expected
4 - run command : service docker status
5 - result is : service is active - this is not necessary if containers are absent.

STR - ISSUE 2 :
1 - follow steps 1 to 5 under "STR - ISSUE 1", if that is not done already
2 - run command : plesk bin extension -u docker
3 - result is : The extension was successfully removed.
4 - run command : ps aux | grep docker
5 - result is : a docker (daemon) process is still present
6 - run command : service docker status
7 - result is : service is active - this is not good if the extension is deleted.
8 - run command : dpkg -l | grep container
9 - result is : packages docker-ce, docker-ce-cli and containerd.io are still installed - this is not good : see additional information.

NOTE - verify memory usage
1 - run command : ps aux | grep docker
2 - run command : htop -p [pid docker daemon found in step 1]​

ACTUAL RESULT:

Results are given in the STR - see above.​

EXPECTED RESULT:

Docker daemon should be

a) after installation and before activation of containers :

- inactive : command service docker status should return inactive state
- inactive : command systemctl list-unit-files | grep docker should return the value enabled

AND

b) after uninstallation via command plesk bin extension -u docker resulting in :

- the disabled state, equivalent to running : systemctl disable docker
- a cleanup of packages, equivalent to running : apt-get purge containerd.io docker-ce docker-ce-cli​

ANY ADDITIONAL INFORMATION:

Additional testing suggests that a multitude of minor problems can occur if the containerd.io package is not removed, even if docker-ce and docker-ce- cli packages are removed.

A reinstall of the Docker extension will install docker-ce and docker-ce-clie without issues.

However, the Docker extension will not be installed due to conflicts related to the remaining package containerd.io - that is a serious problem : running from the CLI, one gets sufficient information to take appropriate actions, but the Plesk Panel method of installing the Docker extension does not give sufficient information to act appropriately.​

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:

Confirm bug​

 

[IgorG]

Thank you!
This bug is confirmed and submitted as PPPM-5422

 

[AYamshanov]

Issue #1:
The Docker extension interacts with Docker service. If your docker service is stopped, you can't check are there any containers or not and understand what is the reason for the stopped status.

# service docker stop
# docker ps -a
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
#

Issue #2:
Let's imagine that you have a Docker service with containers and decided to remove the Docker extension (for any reason). It can cause that you lose the required containers only because you remove the Docker extension.

Currently, Plesk does not provide an ability to ask a choice of what to do next when you delete an extension (save current state/data/processes/services/etc. or revert everything to the default state). We have this in our backlog. I believe that this is not a bug, but a new functionality.