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

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

Источник

ExecStart=/usr/bin/dockerd -H fd:// (code=exited, status=1/FAILURE) __ Docker Installation Failed #7170

Problem description

Greetings!
I got the last released of Docker for Debian[Kali Linux] from below link:
https://download.docker.com/linux/debian/dists/jessie/pool/stable/amd64/

How to fix the problem !?

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

Even i removed and purged the downloaded + installed (failed) Docker and tried to install docker via built-in Debian repositories. but again failed.

debian [39.8 MB] Fetched 39.8 MB in 17s (2,343 kB/s) Selecting previously unselected package docker-ce. (Reading database . 643658 files and directories currently installed.) Preparing to unpack . /docker-ce_18.06.0

debian_amd64.deb . Unpacking docker-ce (18.06.0

debian) . Setting up docker-ce (18.06.0

debian) . update-rc.d: We have no instructions for the docker init script. update-rc.d: It looks like a non-network service, we enable it. 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; disabled; vendor preset: disabled) Active: activating (auto-restart) (Result: exit-code) since Sat 2018-08-04 15:31:03 +0430; 6ms ago Docs: https://docs.docker.com Process: 15457 ExecStart=/usr/bin/dockerd -H fd:// (code=exited, status=1/FAILURE) Main PID: 15457 (code=exited, status=1/FAILURE) Tasks: 40 (limit: 4915) Memory: 3.2M CGroup: /system.slice/docker.service Aug 04 15:31:03 kalia.ir systemd[1]: Failed to start Docker Application Container Engine. dpkg: error processing package docker-ce (—configure): installed docker-ce package post-installation script subprocess returned error exit status 1 Processing triggers for systemd (239-7) . Processing triggers for man-db (2.8.3-2) . Errors were encountered while processing: docker-ce E: Sub-process /usr/bin/dpkg returned an error code (1) root@kalia:

# systemctl status docker.service ● docker.service — Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; disabled; vendor preset: disabled) Active: failed (Result: exit-code) since Sat 2018-08-04 15:31:05 +0430; 22s ago Docs: https://docs.docker.com Process: 15983 ExecStart=/usr/bin/dockerd -H fd:// (code=exited, status=1/FAILURE) Main PID: 15983 (code=exited, status=1/FAILURE) Aug 04 15:31:04 kalia.ir systemd[1]: docker.service: Failed with result ‘exit-code’. Aug 04 15:31:04 kalia.ir systemd[1]: Failed to start Docker Application Container Engine. Aug 04 15:31:05 kalia.ir systemd[1]: docker.service: Service RestartSec=100ms expired, scheduling restart. Aug 04 15:31:05 kalia.ir systemd[1]: docker.service: Scheduled restart job, restart counter is at 4. Aug 04 15:31:05 kalia.ir systemd[1]: Stopped Docker Application Container Engine. Aug 04 15:31:05 kalia.ir systemd[1]: docker.service: Start request repeated too quickly. Aug 04 15:31:05 kalia.ir systemd[1]: docker.service: Failed with result ‘exit-code’. Aug 04 15:31:05 kalia.ir systemd[1]: Failed to start Docker Application Container Engine. root@kalia:

make sure to check the full logs for the docker service (using journalctl ); you’ll likely find the actual error message in there

Closing this ticket due to its age, and the impending refactor. If you think this is in error, feel free to reopen. Thanks!

I know this isn’t a docker.github.io issue, but I just wanted to throw this out there for anyone else that might come across this thread looking for a solution.

I had the same problem. I had Docker running fine on my other machines (laptops and desktops). I was, at the time, running Ubuntu 16.04 on all of my machines.

I could not get the dockerd service to start successfully on my shiny new 16.04 laptop. I would get the same error as the OP here.

I spent hours trying different things with no luck. It turned out it was because my VPN (ExpressVPN) was running. I disconnected the VPN and everything was fine.

I found that it was a networking issue because I ran:

Hope this helps.

running dockerd manually helped me to analyze my problem too.

Thanks for mentioning it!

(base) blueberry@linux:/media/blueberry/595d3676-4ee2-4aa9-b39d-bcd412f9f69a$ sudo dockerd -D
INFO[2022-06-06T15:58:33.871319913+08:00] Starting up
DEBU[2022-06-06T15:58:33.871877590+08:00] Listener created for HTTP on unix (/var/run/docker.sock)
INFO[2022-06-06T15:58:33.872412225+08:00] detected 127.0.0.53 nameserver, assuming systemd-resolved, so using resolv.conf: /run/systemd/resolve/resolv.conf
DEBU[2022-06-06T15:58:33.873148114+08:00] Golang’s threads limit set to 55080
INFO[2022-06-06T15:58:33.873844627+08:00] parsed scheme: «unix» module=grpc
INFO[2022-06-06T15:58:33.873893628+08:00] scheme «unix» not registered, fallback to default scheme module=grpc
DEBU[2022-06-06T15:58:33.873935045+08:00] metrics API listening on /var/run/docker/metrics.sock
INFO[2022-06-06T15:58:33.873966837+08:00] ccResolverWrapper: sending update to cc: <[] > module=grpc
INFO[2022-06-06T15:58:33.874173341+08:00] ClientConn switching balancer to «pick_first» module=grpc
INFO[2022-06-06T15:58:33.875950208+08:00] parsed scheme: «unix» module=grpc
INFO[2022-06-06T15:58:33.876002126+08:00] scheme «unix» not registered, fallback to default scheme module=grpc
INFO[2022-06-06T15:58:33.876063668+08:00] ccResolverWrapper: sending update to cc: <[] > module=grpc
INFO[2022-06-06T15:58:33.876108294+08:00] ClientConn switching balancer to «pick_first» module=grpc
DEBU[2022-06-06T15:58:33.877191273+08:00] processing event stream module=libcontainerd namespace=plugins.moby
DEBU[2022-06-06T15:58:33.877239399+08:00] Using default logging driver json-file
DEBU[2022-06-06T15:58:33.877380276+08:00] [graphdriver] priority list: [btrfs zfs overlay2 fuse-overlayfs aufs overlay devicemapper vfs]
DEBU[2022-06-06T15:58:33.877542446+08:00] zfs command is not available: exec: «zfs»: executable file not found in $PATH storage-driver=zfs
ERRO[2022-06-06T15:58:33.882766877+08:00] failed to mount overlay: no such device storage-driver=overlay2
ERRO[2022-06-06T15:58:33.882974548+08:00] exec: «fuse-overlayfs»: executable file not found in $PATH storage-driver=fuse-overlayfs
ERRO[2022-06-06T15:58:33.885866185+08:00] AUFS was not found in /proc/filesystems storage-driver=aufs
ERRO[2022-06-06T15:58:33.890124306+08:00] failed to mount overlay: no such device storage-driver=overlay
DEBU[2022-06-06T15:58:33.893542995+08:00] Initialized graph driver vfs
DEBU[2022-06-06T15:58:33.893942878+08:00] No quota support for local volumes in /var/lib/docker/volumes: Filesystem does not support, or has not enabled quotas
WARN[2022-06-06T15:58:33.897885701+08:00] Your kernel does not support cgroup memory limit
WARN[2022-06-06T15:58:33.897931202+08:00] Your kernel does not support CPU realtime scheduler
WARN[2022-06-06T15:58:33.898023954+08:00] Unable to find blkio cgroup in mounts
WARN[2022-06-06T15:58:33.898059830+08:00] Unable to find pids cgroup in mounts
DEBU[2022-06-06T15:58:33.898526797+08:00] Max Concurrent Downloads: 3
DEBU[2022-06-06T15:58:33.898569673+08:00] Max Concurrent Uploads: 5
DEBU[2022-06-06T15:58:33.898602923+08:00] Max Download Attempts: 5
INFO[2022-06-06T15:58:33.898670299+08:00] Loading containers: start.
DEBU[2022-06-06T15:58:33.898800094+08:00] Option Experimental: false
DEBU[2022-06-06T15:58:33.898841219+08:00] Option DefaultDriver: bridge
DEBU[2022-06-06T15:58:33.898873887+08:00] Option DefaultNetwork: bridge
DEBU[2022-06-06T15:58:33.898910637+08:00] Network Control Plane MTU: 1500
DEBU[2022-06-06T15:58:33.898898387+08:00] processing event stream module=libcontainerd namespace=moby
WARN[2022-06-06T15:58:33.902704125+08:00] Running modprobe bridge br_netfilter failed with message: modprobe: WARNING: Module bridge not found in directory /lib/modules/5.10.66
modprobe: WARNING: Module br_netfilter not found in directory /lib/modules/5.10.66
, error: exit status 1
WARN[2022-06-06T15:58:33.910898070+08:00] Running iptables —wait -t nat -L -n failed with message: iptables v1.8.4 (legacy): can’t initialize iptables table nat’: Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded. , error: exit status 3 DEBU[2022-06-06T15:58:33.922133280+08:00] /usr/sbin/iptables, [-t filter -C FORWARD -j DOCKER-ISOLATION] DEBU[2022-06-06T15:58:33.930217848+08:00] /usr/sbin/iptables, [-t nat -D PREROUTING -m addrtype —dst-type LOCAL -j DOCKER] DEBU[2022-06-06T15:58:33.938240581+08:00] /usr/sbin/iptables, [-t nat -D OUTPUT -m addrtype —dst-type LOCAL ! —dst 127.0.0.0/8 -j DOCKER] DEBU[2022-06-06T15:58:33.946407692+08:00] /usr/sbin/iptables, [-t nat -D OUTPUT -m addrtype —dst-type LOCAL -j DOCKER] DEBU[2022-06-06T15:58:33.954494010+08:00] /usr/sbin/iptables, [-t nat -D PREROUTING] DEBU[2022-06-06T15:58:33.962472701+08:00] /usr/sbin/iptables, [-t nat -D OUTPUT] DEBU[2022-06-06T15:58:33.971057487+08:00] /usr/sbin/iptables, [-t nat -F DOCKER] DEBU[2022-06-06T15:58:33.977972741+08:00] /usr/sbin/iptables, [-t nat -X DOCKER] DEBU[2022-06-06T15:58:33.984878953+08:00] /usr/sbin/iptables, [-t filter -F DOCKER] DEBU[2022-06-06T15:58:33.991684247+08:00] /usr/sbin/iptables, [-t filter -X DOCKER] DEBU[2022-06-06T15:58:33.998385706+08:00] /usr/sbin/iptables, [-t filter -F DOCKER-ISOLATION-STAGE-1] DEBU[2022-06-06T15:58:34.005031747+08:00] /usr/sbin/iptables, [-t filter -X DOCKER-ISOLATION-STAGE-1] DEBU[2022-06-06T15:58:34.011356657+08:00] /usr/sbin/iptables, [-t filter -F DOCKER-ISOLATION-STAGE-2] DEBU[2022-06-06T15:58:34.018127825+08:00] /usr/sbin/iptables, [-t filter -X DOCKER-ISOLATION-STAGE-2] DEBU[2022-06-06T15:58:34.025012162+08:00] /usr/sbin/iptables, [-t filter -F DOCKER-ISOLATION] DEBU[2022-06-06T15:58:34.031704871+08:00] /usr/sbin/iptables, [-t filter -X DOCKER-ISOLATION] DEBU[2022-06-06T15:58:34.038561791+08:00] /usr/sbin/iptables, [-t nat -n -L DOCKER] DEBU[2022-06-06T15:58:34.042700910+08:00] /usr/sbin/iptables, [-t nat -N DOCKER] DEBU[2022-06-06T15:58:34.049590788+08:00] daemon configured with a 15 seconds minimum shutdown timeout DEBU[2022-06-06T15:58:34.049626081+08:00] start clean shutdown of all containers with a 15 seconds timeout. DEBU[2022-06-06T15:58:34.049687332+08:00] found 0 orphan layers DEBU[2022-06-06T15:58:34.050016921+08:00] Cleaning up old mountid : start. INFO[2022-06-06T15:58:34.050104131+08:00] stopping event stream following graceful shutdown error=» » module=libcontainerd namespace=moby DEBU[2022-06-06T15:58:34.050301885+08:00] Cleaning up old mountid : done. failed to start daemon: Error initializing network controller: error obtaining controller instance: failed to create NAT chain DOCKER: iptables failed: iptables -t nat -N DOCKER: iptables v1.8.4 (legacy): can’t initialize iptables table nat’: Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
(exit status 3)

© 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.

Источник

Installation not working on Ubuntu 19.10 #8891

I’ve tried to install Docker on Ubuntu 19.04. I followed the directions, but I get the following errors:

apt update works correctly:

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

Ubuntu 19.04 is not yet in the list of supported distros for Docker 18.09, but will be coming with Docker 19.03 (beta/release-candidates are available in the «test» channel)

Closing this issue because of the above, but feel free to continue the conversation

@thaJeztah Docker 19.03 has been released, but the installation instructions still yields an error:

Is there a workaround, or can we expect it to land soon?

@ruurtjan the original issue reported above was on Ubuntu 19.04 (although I see the title said «19.10»). Packages are available for ubuntu 19.04 «disco» now, but 19.10 not yet; I think it was released Yesterday; most likely will come with the next Docker release (but that’s still some time out).

In the meantime you can try installing the package for Ubuntu 19.04 on Ubuntu 19.10 (which likely will work, but not tested), and I’ll have a look if it can be added to the nightly builds.

You can install 19.04 and then docker, then update to 19.10

Is there a workaround, or can we expect it to land soon?

In the meantime you can try installing the package for Ubuntu 19.04 on Ubuntu 19.10 (which likely will work, but not tested), and I’ll have a look if it can be added to the nightly builds.

Jep, got hello-world running correctly on Ubuntu 19.10 ( eoan ) with the disco repo using:

In the meantime you can try installing the package for Ubuntu 19.04 on Ubuntu 19.10 (which likely will work, but not tested), and I’ll have a look if it can be added to the nightly builds.

Jep, got hello-world running correctly on Ubuntu 19.10 ( eoan ) with the disco repo using:

This worked for me, thanks

In the meantime you can try installing the package for Ubuntu 19.04 on Ubuntu 19.10 (which likely will work, but not tested), and I’ll have a look if it can be added to the nightly builds.

Jep, got hello-world running correctly on Ubuntu 19.10 ( eoan ) with the disco repo using:

Did not worked for me.

I’ve got the following

Add the «disco» repository, and install docker

Verify the install

Add the «disco» repository, and install docker

Verify the install

Yes! I really missed a step on the installation steps. Thanks for your help!

@rivajunior
Thank you I was able to finally install Docker-CE on Ubuntu / POP_OS 19.10.

@rivajunior
Worked for me as well on my Ubuntu 19.10, Thank you!

This issue should remain open. Problem still persists.

This worked for me!

Unfortunately, I followed the exact steps on Ubuntu Budgie 19.10 and keep getting the same error. Completely removed Docker and tried again 3 times. Same result:

I managed to get the latest release of Docker running on my Kubuntu 19.10 install just by going to snapcraft.io and installing the snap. That easy.

I managed to get the latest release of Docker running on my Kubuntu 19.10 install just by going to snapcraft.io and installing the snap. That easy.

Easy but performance will suffer. Snap packages start up a bit slower. Source (page 2 with Chromium browser as an example).

There should be a way to install the right version that works on 19.10..

I tried installing via Snap, also does not work!

I’m having problems to install Docker on Ubunbtu 19.10

I’m using this script:

sudo ./docker-config.sh 1.25.4

@thaJeztah
I am unable to install also on 19.10, please see #10347 (comment) 😞
PS: re-open this issue as it is not fixed yet.

Hi @TriMoon! There should now be Ubuntu 19.10 packages up. Do you still have this problem?

@chris-crone ill try again later and update this reply. (Currently busy with other important stuff)

Hi @chris-crone, Still facing this problem.

sudo apt-get install docker-ce docker-ce-cli containerd.io
Reading package lists. Done
Building dependency tree
Reading state information. Done
The following NEW packages will be installed:
containerd.io docker-ce docker-ce-cli
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/85.6 MB of archives.
After this operation, 384 MB of additional disk space will be used.
Selecting previously unselected package containerd.io.
(Reading database . 263084 files and directories currently installed.)
Preparing to unpack . /containerd.io_1.2.13-1_amd64.deb .
Unpacking containerd.io (1.2.13-1) .
Selecting previously unselected package docker-ce-cli.
Preparing to unpack . /docker-ce-cli_5%3a19.03.8 3-0 ubuntu-eoan_amd64.deb .
Unpacking docker-ce-cli (5:19.03.8 3-0 ubuntu-eoan) .
Selecting previously unselected package docker-ce.
Preparing to unpack . /docker-ce_5%3a19.03.8 3-0 ubuntu-eoan_amd64.deb .
Unpacking docker-ce (5:19.03.8 3-0 ubuntu-eoan) .
Setting up containerd.io (1.2.13-1) .
Setting up docker-ce-cli (5:19.03.8 3-0 ubuntu-eoan) .
Setting up docker-ce (5:19.03.8 3-0 ubuntu-eoan) .
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 Tue 2020-04-07 22:01:31 EDT; 8ms ago
Docs: https://docs.docker.com
Process: 15790 ExecStart=/usr/bin/dockerd -H fd:// —containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
Main PID: 15790 (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 man-db (2.8.7-3) .
Processing triggers for systemd (242-7ubuntu3.2pop1 1575565723 19.10

6a5852b) .
Errors were encountered while processing:
docker-ce
E: Sub-process /usr/bin/dpkg returned an error code (1)

Nvm got it working. Seems like I had not installed some new os updates. After getting those, rebooting and reinstalling, it installed without any hiccups

Worked for me with
sudo snap install docker

The snap packages won’t install the official packages, and I’ve seen some issues reported when running those, so I would not currently recommend running those.

Источник

Description

After successful docker-ce installation I uninstalled it. The second installation fails.

Steps to reproduce the issue:

I used vagrant to reproduce it:

vagrant init ubuntu/bionic64
vagrant up
vagrant ssh

Then I run the following commands:

curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
sudo add-apt-repository 
   "deb [arch=amd64] https://download.docker.com/linux/ubuntu 
   $(lsb_release -cs) 
   stable"
sudo apt-get -y update
sudo apt-get -y install docker-ce docker-ce-cli containerd.io
sudo apt-get -y purge docker-ce docker-ce-cli containerd.io
sudo apt-get -y install docker-ce docker-ce-cli containerd.io

Describe the results you received:

(I put the above commands in a shell script and run bash -x on that. But I get same failure if I enter commands directly).

+ curl -fsSL https://download.docker.com/linux/ubuntu/gpg
+ sudo apt-key add -
Warning: apt-key output should not be parsed (stdout is not a terminal)
OK
++ lsb_release -cs
+ sudo add-apt-repository 'deb [arch=amd64] https://download.docker.com/linux/ubuntu    bionic    stable'
Hit:1 https://download.docker.com/linux/ubuntu bionic InRelease
Hit:2 http://archive.ubuntu.com/ubuntu bionic InRelease
Hit:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
Hit:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease
Hit:5 http://security.ubuntu.com/ubuntu bionic-security InRelease
Reading package lists...
+ sudo apt-get -y update
Hit:1 http://security.ubuntu.com/ubuntu bionic-security InRelease
Hit:2 http://archive.ubuntu.com/ubuntu bionic InRelease
Hit:3 https://download.docker.com/linux/ubuntu bionic InRelease
Hit:4 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
Hit:5 http://archive.ubuntu.com/ubuntu bionic-backports InRelease
Reading package lists...
+ sudo apt-get -y install docker-ce docker-ce-cli containerd.io
Reading package lists...
Building dependency tree...
Reading state information...
containerd.io is already the newest version (1.4.3-1).
docker-ce-cli is already the newest version (5:20.10.0~3-0~ubuntu-bionic).
docker-ce is already the newest version (5:20.10.0~3-0~ubuntu-bionic).
0 upgraded, 0 newly installed, 0 to remove and 7 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up docker-ce (5:20.10.0~3-0~ubuntu-bionic) ...
Setting up docker-ce-rootless-extras (5:20.10.0~3-0~ubuntu-bionic) ...
W: APT had planned for dpkg to do more than it reported back (3 vs 7).
   Affected packages: docker-ce:amd64
+ sudo apt-get -y purge docker-ce docker-ce-cli containerd.io
Reading package lists...
Building dependency tree...
Reading state information...
The following packages were automatically installed and are no longer required:
  libltdl7 pigz
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  containerd.io* docker-ce* docker-ce-cli* docker-ce-rootless-extras*
0 upgraded, 0 newly installed, 4 to remove and 7 not upgraded.
After this operation, 445 MB disk space will be freed.
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 60080 files and directories currently installed.)
Removing docker-ce-rootless-extras (5:20.10.0~3-0~ubuntu-bionic) ...
Removing docker-ce (5:20.10.0~3-0~ubuntu-bionic) ...
Warning: Stopping docker.service, but it can still be activated by:
  docker.socket
Removing containerd.io (1.4.3-1) ...
Removing docker-ce-cli (5:20.10.0~3-0~ubuntu-bionic) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 59851 files and directories currently installed.)
Purging configuration files for docker-ce (5:20.10.0~3-0~ubuntu-bionic) ...
Purging configuration files for containerd.io (1.4.3-1) ...
Processing triggers for systemd (237-3ubuntu10.43) ...
Processing triggers for ureadahead (0.100.0-21) ...
+ sudo apt-get -y install docker-ce docker-ce-cli containerd.io
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  docker-ce-rootless-extras
Suggested packages:
  aufs-tools cgroupfs-mount | cgroup-lite
Recommended packages:
  slirp4netns
The following NEW packages will be installed:
  containerd.io docker-ce docker-ce-cli docker-ce-rootless-extras
0 upgraded, 4 newly installed, 0 to remove and 7 not upgraded.
Need to get 0 B/101 MB of archives.
After this operation, 445 MB of additional disk space will be used.
Selecting previously unselected package containerd.io.
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 59846 files and directories currently installed.)
Preparing to unpack .../containerd.io_1.4.3-1_amd64.deb ...
Unpacking containerd.io (1.4.3-1) ...
Selecting previously unselected package docker-ce-cli.
Preparing to unpack .../docker-ce-cli_5%3a20.10.0~3-0~ubuntu-bionic_amd64.deb ...
Unpacking docker-ce-cli (5:20.10.0~3-0~ubuntu-bionic) ...
Selecting previously unselected package docker-ce.
Preparing to unpack .../docker-ce_5%3a20.10.0~3-0~ubuntu-bionic_amd64.deb ...
Unpacking docker-ce (5:20.10.0~3-0~ubuntu-bionic) ...
Selecting previously unselected package docker-ce-rootless-extras.
Preparing to unpack .../docker-ce-rootless-extras_5%3a20.10.0~3-0~ubuntu-bionic_amd64.deb ...
Unpacking docker-ce-rootless-extras (5:20.10.0~3-0~ubuntu-bionic) ...
Setting up containerd.io (1.4.3-1) ...
Created symlink /etc/systemd/system/multi-user.target.wants/containerd.service → /lib/systemd/system/containerd.service.
Setting up docker-ce-cli (5:20.10.0~3-0~ubuntu-bionic) ...
Setting up docker-ce (5:20.10.0~3-0~ubuntu-bionic) ...
Created symlink /etc/systemd/system/multi-user.target.wants/docker.service → /lib/systemd/system/docker.service.
Created symlink /etc/systemd/system/sockets.target.wants/docker.socket → /lib/systemd/system/docker.socket.
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 Mon 2020-12-14 22:27:40 UTC; 7ms ago
     Docs: https://docs.docker.com
  Process: 7435 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock �[0;1;31m(code=exited, status=1/FAILURE)�[0m
 Main PID: 7435 (code=exited, status=1/FAILURE)

Dec 14 22:27:40 ubuntu-bionic systemd[1]: �[0;1;39m�[0;1;31m�[0;1;39mdocker.service: Main process exited, code=exited, status=1/FAILURE�[0m
Dec 14 22:27:40 ubuntu-bionic systemd[1]: �[0;1;39m�[0;1;31m�[0;1;39mdocker.service: Failed with result 'exit-code'.�[0m
Dec 14 22:27:40 ubuntu-bionic systemd[1]: �[0;1;31m�[0;1;39m�[0;1;31mFailed to start Docker Application Container Engine.�[0m
dpkg: error processing package docker-ce (--configure):
 installed docker-ce package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of docker-ce-rootless-extras:
 docker-ce-rootless-extras depends on docker-ce; however:
  Package docker-ce is not configured yet.

dpkg: error processing package docker-ce-rootless-extras (--configure):
 dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
Processing triggers for ureadahead (0.100.0-21) ...
Processing triggers for systemd (237-3ubuntu10.43) ...
Errors were encountered while processing:
 docker-ce
 docker-ce-rootless-extras
E: Sub-process /usr/bin/dpkg returned an error code (1)

Describe the results you expected:

I would expect that I could install docker a second time. I had also no success if I add docker-ce-rootless-extras to docker purge.

Additional information you deem important (e.g. issue happens only occasionally):

Looks similar docker/for-linux#1154 (report of version included in repository).

Similar to #41781 but there docker installation succeed and the rootless scripts fails.

Output of docker version:

(after running above installation steps)

Client: Docker Engine - Community
 Version:           20.10.0
 API version:       1.41
 Go version:        go1.13.15
 Git commit:        7287ab3
 Built:             Tue Dec  8 18:59:53 2020
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

Output of docker info:

(after running above installation steps)

Client:
 Context:    default
 Debug Mode: false
 Plugins:
  app: Docker App (Docker Inc., v0.9.1-beta3)
  buildx: Build with BuildKit (Docker Inc., v0.4.2-docker)

Server:
ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
errors pretty printing info

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

vagrant virtual box with ubuntu 18.04.

I’m trying to get Docker installed on a machine with Debian 8 (Jessie), but I always seem to run into errors no matter what I try.

Using these instructions: https://docs.docker.com/install/linux/docker-ce/debian

Checking the kernal:

uname -r
3.16.0-4-686-pae

The fateful moment:

sudo apt-get install docker-ce

Setting up docker-ce (18.06.1~ce~3-0~debian) …
Installing new version of config file /etc/bash_completion.d/docker …
Job for docker.service failed. See ‘systemctl status docker.service’ and ‘journalctl -xn’ 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
Processing triggers for libc-bin (2.19-18+deb8u10) …
Errors were encountered while processing:
docker-ce
E: Sub-process /usr/bin/dpkg returned an error code (1)

I also tried installing directly from a package: https://download.docker.com/linux/debian/dists/jessie/pool/stable/amd64/
(Selecting version 17.03.2)

And after installing the dependencies, things still don’t work:

sudo dpkg --install  docker-ce_17.03.2_ce-0_debian-jessie_amd64.deb

(Reading database ... 169325 files and directories currently installed.)
Preparing to unpack docker-ce_17.03.2_ce-0_debian-jessie_amd64.deb ...
Unpacking docker-ce (17.03.2~ce-0~debian-jessie) over (17.03.2~ce-0~debian-jessie) ...
Setting up docker-ce (17.03.2~ce-0~debian-jessie) ...
Job for docker.service failed. See 'systemctl status docker.service' and 'journalctl -xn' for details.
invoke-rc.d: initscript docker, action "start" failed.
dpkg: error processing package docker-ce (--install):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for man-db (2.7.0.2-5) ...
Processing triggers for systemd (215-17+deb8u7) ...
Errors were encountered while processing:
 docker-ce

I also looked at this article: http://www.boynux.com/docker-jessie/
But I didn’t even get past the first step:

curl https://get.docker.com | sh

Either your platform is not easily detectable or is not supported by this
installer script.
Please visit the following URL for more detailed installation instructions:

https://docs.docker.com/engine/installation/

Between every one of these attempts I did a

sudo apt-get remove docker docker-engine docker.io docker-ce
sudo apt-get update