Dpkg error processing package docker ce

can not successfully install docker-ce on ubuntu 16.04 ? why ,Can you help me? #33689

# apt install docker-ce

Jun 15 17:56:40 instance-4u1z1xql dockerd[31531]: time=»2017-06-15T17:56:40.289072089+08:00″ level=info msg=»libcontainerd: new containerd process, pid: 31539″
Jun 15 17:56:41 instance-4u1z1xql kernel: aufs: disagrees about version of symbol module_layout
Jun 15 17:56:41 instance-4u1z1xql dockerd[31531]: time=»2017-06-15T17:56:41.299671154+08:00″ level=error msg=»‘overlay’ not found as a supported filesystem on this host. Jun 15 17:56:41 instance-4u1z1xql kernel: overlay: disagrees about version of symbol module_layout
Jun 15 17:56:41 instance-4u1z1xql dockerd[31531]: time=»2017-06-15T17:56:41.301776138+08:00″ level=error msg=»‘overlay’ not found as a supported filesystem on this host. Jun 15 17:56:41 instance-4u1z1xql kernel: overlay: disagrees about version of symbol module_layout
Jun 15 17:56:41 instance-4u1z1xql kernel: libcrc32c: disagrees about version of symbol module_layout
Jun 15 17:56:41 instance-4u1z1xql kernel: device-mapper: table: 252:0: thin-pool: unknown target type
Jun 15 17:56:41 instance-4u1z1xql kernel: device-mapper: ioctl: error adding target to table
Jun 15 17:56:41 instance-4u1z1xql dockerd[31531]: Error starting daemon: error initializing graphdriver: devicemapper: Error running deviceCreate (CreatePool) dm_task_runJun 15 17:56:41 instance-4u1z1xql systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Jun 15 17:56:41 instance-4u1z1xql systemd[1]: Failed to start Docker Application Container Engine.
— Subject: Unit docker.service has failed
— Defined-By: systemd
— Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

The text was updated successfully, but these errors were encountered:

@whxloveyrh DId you removed the previous version of docker?

It seems like your system ports are busy, do check docker ps -a , below is the process to install docker community edition :

Remove previous version of docker and docker engine
$ sudo apt-get remove docker docker-engine

Allow apt to use repo over https
$ sudo apt-get install apt-transport-https ca-certificates curl software-properties-common

Add Docker official’s GPG Key
$ curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add —

Setting up stable repository
$ sudo add-apt-repository «deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable»

Above command returns the name of Ubuntu distribution like «Xenial»

Install Docker
$ sudo apt-get update
$ sudo apt-get install docker-ce

Источник

Docker-ce fails to install in Debian GNU/Linux 10 #769

Expected behavior

Actual behavior

Installation fails with this apt report:

Steps to reproduce the behavior

Output of docker version :

Output of docker info :

Output of cat /etc/issue :

Output of uname -a :

Output of # cat /etc/default/grub :

Additional environment details (AWS, VirtualBox, physical, etc.)

The text was updated successfully, but these errors were encountered:

Test run docker run hello-world

i’m find error.
if first run docker engine run service opevnp result fail, but if
` «
systemctl stop openvpn-client@dev-vm
systemctl restart docker.service
systemctl start openvpn-client@dev-vm

I can confirm this on a fresh Debian 10 install (and confirm the workaround of shutting down openvpn)

That’s quite strange.
Is there something in the docker daemon logs?

Can you check the logs for the docker daemon? (something like journalctl -xu docker ). Is it possible that OpenVPN reserves all ip-ranges, and therefore the docker daemon is unable to pick a suitable range for its internal networks? See #1050 (comment)

Given that by default, docker has socket-activation enabled, it’s possible that docker run hello-world tries to connect to the /var/run/docker.sock socket, which will trigger socket activation (which tries to start the daemon), then (because of the problem above), the daemon fails to start, causing the socket connection to be closed, which is shown as read: connection reset by peer

I got the very same issue trying to install on a gcp compute engine . journactl -u docker shows :

And if I look installation output, I can see:

If these are unattended / non-interactive installs, I wonder if it’s related to docker/docker-ce-packaging#331 / docker/docker-ce-packaging#486

might be, as I’m installing through metadata.startup_script (non interactive script running at compute startup).
If I comment apt install and do it by hand, everything works correctly

updating to debian 11 solved this for me.

© 2023 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

Docker Fails to Start After Upgrade from 19.03.14 to 20.10.01 on Debian #1177

Expected behavior

After upgrading docker-ce and docker-ce-cli the docker service should be restart and be brought up successfully.

Actual behavior

Docker fails to start after upgrade

Steps to reproduce the behavior

1. Run apt upgrade to upgrade docker-ce and docker-ce-cli as available:

1. The docker service fails to start during the upgrade preventing a successful upgrade.
   Logs:

Output of systemctl status docker.service :

Additional environment details (AWS, VirtualBox, physical, etc.)
This is running on Debian Buster (10) with all other packages up-to-date.

The text was updated successfully, but these errors were encountered:

Do the logs show anything useful?

This output is a bit confusing (saw something similar in another issue that was posted); for some reason, systemd seems to be triggering the rc.d scripts as well (it should skip them if there’s a systemd unit with the same name);

i’m having a similar problem, i think it is linked to cgroups,

output of sudo service docker status :

output of sudo journalctl -xeu docker.service :

if i try to launch dockerd manualy : sudo dockerd

I found there is an open issue about this:

I fixed it using the fix described in this issue:

adding the systemd.unified_cgroup_hierarchy=0 kernel parameters

to do so, i edited the file /etc/default/grub

and added this line (check if it doesn’t exist before adding the full line, only add the parameter if it exists)

then run update-grub

after a reboot, the docker daemon worked again

i’m thinking this was caused by an update in cgroup at one point during last week

Источник

Upgrading from 18.09.0 to 18.09.1 fails on Ubuntu 16.04 #567

Expected behavior

The upgrade should complete normally and restart the Docker daemon.

Actual behavior

The upgrade replaces the files, but the daemon is not restarted, and the package is considered unconfigured by dpkg.

Steps to reproduce the behavior

On a clean Ubuntu 16.04 system:

# apt update [. snipped . ] root@ubuntu:

# apt install docker-ce=5:18.09.0

ubuntu-xenial [. snipped . ] root@ubuntu:

# apt install docker-ce=5:18.09.1

ubuntu-xenial Reading package lists. Done Building dependency tree Reading state information. Done The following packages will be upgraded: docker-ce 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 17.4 MB of archives. After this operation, 36.9 kB of additional disk space will be used. Get:1 https://download.docker.com/linux/ubuntu xenial/stable amd64 docker-ce amd64 5:18.09.1

ubuntu-xenial [17.4 MB] Fetched 17.4 MB in 1min 13s (235 kB/s) (Reading database . 83262 files and directories currently installed.) Preparing to unpack . /docker-ce_5%3a18.09.1

ubuntu-xenial_amd64.deb . Unpacking docker-ce (5:18.09.1

ubuntu-xenial) over (5:18.09.0

ubuntu-xenial) . Processing triggers for systemd (229-4ubuntu21.15) . Processing triggers for ureadahead (0.100.0-19) . Setting up docker-ce (5:18.09.1

ubuntu-xenial) . update-alternatives: using /usr/bin/dockerd-ce to provide /usr/bin/dockerd (dockerd) in auto mode A dependency job for docker.service failed. See ‘journalctl -xe’ for details. invoke-rc.d: initscript docker, action «start» failed. ● docker.service — Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2019-01-21 11:38:27 UTC; 1min 31s ago Docs: https://docs.docker.com Main PID: 3279 (dockerd) CGroup: /system.slice/docker.service └─3279 /usr/bin/dockerd -H unix:// Jan 21 11:38:26 ubuntu dockerd[3279]: time=»2019-01-21T11:38:26.336833164Z» level=warning msg=»Your kernel does not support cgroup rt runtime» Jan 21 11:38:26 ubuntu dockerd[3279]: time=»2019-01-21T11:38:26.339150924Z» level=info msg=»Loading containers: start.» Jan 21 11:38:26 ubuntu dockerd[3279]: time=»2019-01-21T11:38:26.709115148Z» level=info msg=»Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. IP address» Jan 21 11:38:26 ubuntu dockerd[3279]: time=»2019-01-21T11:38:26.855658023Z» level=info msg=»Loading containers: done.» Jan 21 11:38:26 ubuntu dockerd[3279]: time=»2019-01-21T11:38:26.888748211Z» level=info msg=»Docker daemon» commit=4d60db4 graphdriver(s)=overlay2 version=18.09.0 Jan 21 11:38:26 ubuntu dockerd[3279]: time=»2019-01-21T11:38:26.889088034Z» level=info msg=»Daemon has completed initialization» Jan 21 11:38:27 ubuntu systemd[1]: Started Docker Application Container Engine. Jan 21 11:38:27 ubuntu dockerd[3279]: time=»2019-01-21T11:38:27.523891180Z» level=info msg=»API listen on /var/run/docker.sock» Jan 21 11:39:58 ubuntu systemd[1]: Dependency failed for Docker Application Container Engine. Jan 21 11:39:58 ubuntu systemd[1]: docker.service: Job docker.service/start failed with result ‘dependency’. Hint: Some lines were ellipsized, use -l to show in full. dpkg: error processing package docker-ce (—configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for systemd (229-4ubuntu21.15) . Processing triggers for ureadahead (0.100.0-19) . Errors were encountered while processing: docker-ce E: Sub-process /usr/bin/dpkg returned an error code (1)»>

Output of docker version :

(This is after the upgrade, since that’s the more interesting output.)

Output of docker info :

Additional environment details (AWS, VirtualBox, physical, etc.)
N/A

The text was updated successfully, but these errors were encountered:

Источник

docker-ce package is missing for Ubuntu «Disco Dingo» 19.04 x86_64 #533

18.10 (Cosmic) problem tags edge/nightly:

The text was updated successfully, but these errors were encountered:

I personally am using the cosmic stable builds on disco, and they are working for me.

docker-ce and docker-ce-cli packages are still missing for Disco stable builds

@edno Stable builds for Disco will be added with the release of Docker CE 19.03.0,

If you’d like to try out the builds you can install them through our test channel:

@seemethere Thanks for the news!

I see this issue was closed, but am experiencing it with 19.04. I have followed the official installation instructions as well as a Medium article, but I see no installation candidate:

I.e. this issue should probably closed once the official packages are released.

The docker.io Ubuntu package looks fairly recent, at 18.09:
https://packages.ubuntu.com/disco/docker.io

However, the official install instructions for Docker CE say to uninstall docker.io:

Running the curl -fsSL get.docker.com | CHANNEL=test sh command installs Docker 19.03 for me.

On Disco Dingo I did (as manual says)

sudo add-apt-repository
«deb [arch=amd64] https://download.docker.com/linux/ubuntu
$(lsb_release -cs)
stable»
Then
sudo apt-get install docker-ce docker-ce-cli containerd.io

And all I got is these errors:

Reading package lists. Done
Building dependency tree
Reading state information. Done
Package docker-ce is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package ‘docker-ce’ has no installation candidate
E: Unable to locate package docker-ce-cli

@gitowiec As state a few comments before:

«Stable builds for Disco will be added with the release of Docker CE 19.03.0.»

This release isn’t out yet. Ubuntu did publish 18.09 with package «docker.io», I used that one and works fine so far. If you are looking for a long-term solution I would wait for the 19.03 Docker-CE release.

I edited the entry in /etc/apt/sources.list and switched from
deb [arch=amd64] https://download.docker.com/linux/ubuntu disco stable
to
deb [arch=amd64] https://download.docker.com/linux/ubuntu bionic stable
and I got error:

groupadd: cannot lock /etc/group; try again later.
dpkg: error processing package docker-ce (—configure):
installed docker-ce package post-installation script subprocess returned error exit status 10
Processing triggers for systemd (240-6ubuntu5) .
Processing triggers for man-db (2.8.5-2) .
Processing triggers for libc-bin (2.29-0ubuntu2) .
Errors were encountered while processing:
docker-ce
E: Sub-process /usr/bin/dpkg returned an error code (1)

What should I do?

@gitowiec You can’t install the Bionic package in a Disco Dingo release. Revert that change you just did and do this:

This will install Docker 18.09.

Unfortunately I got another problem

sudo apt install docker.io
Reading package lists. Done
Building dependency tree
Reading state information. Done
The following additional packages will be installed:
bridge-utils ubuntu-fan
Suggested packages:
ifupdown debootstrap docker-doc rinse zfs-fuse | zfsutils
The following packages will be REMOVED:
docker-ce-cli
The following NEW packages will be installed:
bridge-utils docker.io ubuntu-fan
0 upgraded, 3 newly installed, 1 to remove and 40 not upgraded.
Need to get 30.8 MB of archives.
After this operation, 85.9 MB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://archive.ubuntu.com/ubuntu disco/main amd64 bridge-utils amd64 1.6-2ubuntu1 [30.5 kB]
Get:2 http://archive.ubuntu.com/ubuntu disco/universe amd64 docker.io amd64 18.09.5-0ubuntu1 [30.7 MB]
Get:3 http://archive.ubuntu.com/ubuntu disco/main amd64 ubuntu-fan all 0.12.12 [34.6 kB]
Fetched 30.8 MB in 3s (8930 kB/s)
Preconfiguring packages .
(Reading database . 200640 files and directories currently installed.)
Removing docker-ce-cli (5:18.09.6 3-0 ubuntu-bionic) .
Selecting previously unselected package bridge-utils.
(Reading database . 200452 files and directories currently installed.)
Preparing to unpack . /bridge-utils_1.6-2ubuntu1_amd64.deb .
Unpacking bridge-utils (1.6-2ubuntu1) .
Selecting previously unselected package docker.io.
Preparing to unpack . /docker.io_18.09.5-0ubuntu1_amd64.deb .
Unpacking docker.io (18.09.5-0ubuntu1) .
Selecting previously unselected package ubuntu-fan.
Preparing to unpack . /ubuntu-fan_0.12.12_all.deb .
Unpacking ubuntu-fan (0.12.12) .
Setting up docker.io (18.09.5-0ubuntu1) .
Installing new version of config file /etc/init.d/docker .
Installing new version of config file /etc/init/docker.conf .
Adding group docker’ (GID 132) . groupadd: cannot lock /etc/group; try again later. addgroup: /sbin/groupadd -g 132 docker’ returned error code 10. Exiting.
dpkg: error processing package docker.io (—configure):
installed docker.io package post-installation script subprocess returned error exit status 1
Setting up bridge-utils (1.6-2ubuntu1) .
Setting up ubuntu-fan (0.12.12) .
Created symlink /etc/systemd/system/multi-user.target.wants/ubuntu-fan.service → /lib/systemd/system/ubuntu-fan.service.
Processing triggers for man-db (2.8.5-2) .
Processing triggers for systemd (240-6ubuntu5) .
Errors were encountered while processing:
docker.io
E: Sub-process /usr/bin/dpkg returned an error code (1)

Sorry everyone if this is a bit off-topic.

@gitowiec This appears to be the problem:

Adding group docker’ (GID 132) . groupadd: cannot lock /etc/group; try again later. addgroup: /sbin/groupadd -g 132 docker’ returned error code 10. Exiting.

You should have permission to edit that file, since you are using sudo ( sudo apt install ). Maybe you can run this to get some clues as to what is going on?: sudo lsof +D /etc (lsof lists open files and tells you details of why they are open. Should show you why /etc/group is open and in-use.)

Also, you might try simply rebooting your computer and trying again, since this may close the program tying up /etc/group .

There is also a stackoverflow answer suggesting to do this: sudo mount -o remount,rw /
source: https://superuser.com/a/820189

You can try that if none of the other things work.

Thanks for fast response. I think the problem is my Ubuntu installation which is not quite full fledged installation. I made it on usb from live cd with mkusb. I think it just binds /etc from the «cdrom» partition which is read only. I wanted go shortcut but instead I ended with double work to do because now I have to begin from the start and make full install.

Источник

I had a similar issue. After Ubuntu upgrade from 18.04.4 to 20.04.2 docker would not start, and errored when trying to install, remove, purge, repair it. (VPN is outside of my control).

$ sudo apt-get purge -y docker-ce
...
1 not fully installed or removed.
...
Removing docker-ce (5:20.10.4~3-0~ubuntu-bionic) ...
Job for docker.service canceled.
invoke-rc.d: initscript docker, action "stop" failed.
dpkg: error processing package docker-ce (--remove):
 installed docker-ce package pre-removal script subprocess returned error exit status 1
dpkg: too many errors, stopping
dpkg: error while cleaning up:
 installed docker-ce package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 docker-ce
Processing was halted because there were too many errors.
E: Sub-process /usr/bin/dpkg returned an error code (1)

I had both docker.io from Debian/Ubuntu and docker-ce from docker.com installed. This post discusses the differences.

dpkg -l | grep -i docker

Looks for me it was choking on containerd which would not start. You can check messages in /var/log/syslog

Removing folders, uninstalling all docker packages and reinstalling docker.io worked.

NOTE: I did not care about previous images or containers, if you do then this might NOT work for you.

$ sudo rm -rf /var/lib/containerd/
$ sudo rm -rf /var/lib/docker/
$ sudo apt-get purge -y docker-ce docker-ce-cli docker.io containerd.io
$ sudo apt-get install docker.io

@amitkumarj441
root@instance-4u1z1xql:# docker
The program ‘docker’ is currently not installed. You can install it by typing:
apt install docker.io
root@instance-4u1z1xql:# apt remove docker docker-engine

Reading package lists... Done
Building dependency tree       
Reading state information... Done
Package 'docker-engine' is not installed, so not removed
Package 'docker' is not installed, so not removed
The following packages were automatically installed and are no longer required:
  aufs-tools cgroupfs-mount linux-headers-4.4.0-66 linux-headers-4.4.0-66-generic sbsigntool
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 94 not upgraded.

root@instance-4u1z1xql:# apt install apt-transport-https cat
catch catcodec catdoc catdvi catfish catkin
root@instance-4u1z1xql:# apt install apt-transport-https ca-certificates curl software-properties-common

Reading package lists... Done
Building dependency tree       
Reading state information... Done
ca-certificates is already the newest version (20160104ubuntu1).
apt-transport-https is already the newest version (1.2.20).
curl is already the newest version (7.47.0-1ubuntu2.2).
software-properties-common is already the newest version (0.96.20.7).
The following packages were automatically installed and are no longer required:
  aufs-tools cgroupfs-mount linux-headers-4.4.0-66 linux-headers-4.4.0-66-generic sbsigntool
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 94 not upgraded.

root@instance-4u1z1xql:# curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key ad
d —
OK
root@instance-4u1z1xql:# apt-key fingerprint 0EBFCD88

pub   4096R/0EBFCD88 2017-02-22
      Key fingerprint = 9DC8 5822 9FC7 DD38 854A  E2D8 8D81 803C 0EBF CD88
uid                  Docker Release (CE deb) <docker@docker.com>
sub   4096R/F273FCD8 2017-02-22

root@instance-4u1z1xql:# add-apt-repository «deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable»
root@instance-4u1z1xql:# lsb_release -cs
xenial
root@instance-4u1z1xql:~# apt update

Hit:1 http://mirrors.baidubce.com/ubuntu xenial InRelease
Hit:2 http://mirrors.baidubce.com/ubuntu xenial-updates InRelease
Hit:3 http://mirrors.baidubce.com/ubuntu xenial-security InRelease
Hit:4 https://download.docker.com/linux/ubuntu xenial InRelease
Reading package lists... Done
Building dependency tree       
Reading state information... Done
94 packages can be upgraded. Run 'apt list --upgradable' to see them.

root@instance-4u1z1xql:~# apt install docker-ce

Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  linux-headers-4.4.0-66 linux-headers-4.4.0-66-generic sbsigntool
Use 'apt autoremove' to remove them.
The following NEW packages will be installed:
  docker-ce
0 upgraded, 1 newly installed, 0 to remove and 94 not upgraded.
Need to get 0 B/19.3 MB of archives.
After this operation, 89.0 MB of additional disk space will be used.
Selecting previously unselected package docker-ce.
(Reading database ... 114802 files and directories currently installed.)
Preparing to unpack .../docker-ce_17.03.1~ce-0~ubuntu-xenial_amd64.deb ...
Unpacking docker-ce (17.03.1~ce-0~ubuntu-xenial) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for systemd (229-4ubuntu13) ...
Processing triggers for ureadahead (0.100.0-19) ...
Setting up docker-ce (17.03.1~ce-0~ubuntu-xenial) ...
Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details.
invoke-rc.d: initscript docker, action "start" failed.
dpkg: error processing package docker-ce (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 docker-ce
E: Sub-process /usr/bin/dpkg returned an error code (1)

root@instance-4u1z1xql:~# journalctl -xe

Jun 15 19:33:09 instance-4u1z1xql dockerd[13028]: time="2017-06-
15T19:33:09.802502692+08:00" level=info msg="libcontainerd: new containerd process, pid: 13037"
Jun 15 19:33:10 instance-4u1z1xql kernel: libcrc32c: disagrees about version of symbol module_layout
Jun 15 19:33:10 instance-4u1z1xql kernel: device-mapper: table: 252:0: thin-pool: unknown target type
Jun 15 19:33:10 instance-4u1z1xql kernel: device-mapper: ioctl: error adding target to table
Jun 15 19:33:10 instance-4u1z1xql dockerd[13028]: time="2017-06-15T19:33:10.891982725+08:00" level=error msg="[graphdriver] prior storage driver devicemapper failed: devicemJun 15 19:33:10 instance-4u1z1xql dockerd[13028]: Error starting daemon: error initializing graphdriver: devicemapper: Error running deviceCreate (CreatePool) dm_task_run faJun 15 19:33:10 instance-4u1z1xql systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Jun 15 19:33:10 instance-4u1z1xql systemd[1]: Failed to start Docker Application Container Engine.

sudo apt install docker-ce
Чтение списков пакетов… Готово
Построение дерева зависимостей       
Чтение информации о состоянии… Готово
Предлагаемые пакеты:
  aufs-tools
Следующие пакеты будут обновлены:
  docker-ce
Обновлено 1 пакетов, установлено 0 новых пакетов, для удаления отмечено 0 пакетов, и 3 пакетов не обновлено.
Необходимо скачать 24,8 MB архивов.
После данной операции объём занятого дискового пространства возрастёт на 37,9 kB.
Пол:1 https://download.docker.com/linux/ubuntu focal/stable amd64 docker-ce amd64 5:20.10.2~3-0~ubuntu-focal [24,8 MB]
Получено 24,8 MB за 4с (7 050 kB/s)     
(Чтение базы данных … на данный момент установлено 318900 файлов и каталогов.)
Подготовка к распаковке …/docker-ce_5%3a20.10.2~3-0~ubuntu-focal_amd64.deb …
Распаковывается docker-ce (5:20.10.2~3-0~ubuntu-focal) на замену (5:20.10.2~3-0~ubuntu-bionic) …
Настраивается пакет docker-ce (5:20.10.2~3-0~ubuntu-focal) …
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.
invoke-rc.d: initscript docker, action "restart" failed.
● docker.service - Docker Application Container Engine
     Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
     Active: activating (auto-restart) (Result: exit-code) since Wed 2021-01-13 10:12:25 MSK; 4ms ago
TriggeredBy: ● docker.socket
       Docs: https://docs.docker.com
    Process: 24233 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
   Main PID: 24233 (code=exited, status=1/FAILURE)
dpkg: ошибка при обработке пакета docker-ce (--configure):
 installed docker-ce package post-installation script subprocess returned error exit status 1
Обрабатываются триггеры для systemd (245.4-4ubuntu3.3) …
При обработке следующих пакетов произошли ошибки:
 docker-ce
E: Sub-process /usr/bin/dpkg returned an error code (1)

Job for docker.service failed because the control process exited with error code.

See «systemctl status docker.service» and «journalctl -xe» for details.

invoke-rc.d: initscript docker, action «start» failed.

● docker.service — Docker Application Container Engine

Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)

Active: activating (auto-restart) (Result: exit-code) since Wed 2019-08-07 14:50:19 +06; 5ms ago

Docs: https://docs.docker.com

Process: 13091 ExecStart=/usr/bin/dockerd -H fd:// —containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)

Main PID: 13091 (code=exited, status=1/FAILURE)

dpkg: error processing package docker-ce (—configure):

installed docker-ce package post-installation script subprocess returned error exit status 1

Processing triggers for ureadahead (0.100.0-20) …

Processing triggers for systemd (237-3ubuntu10.12) …

Errors were encountered while processing:

docker-ce

E: Sub-process /usr/bin/dpkg returned an error code (1)

still showing error