Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cgroups: cannot found cgroup mount destination: unknown #219

Open
2 of 3 tasks
xgenvn opened this issue Feb 5, 2018 · 149 comments
Open
2 of 3 tasks

cgroups: cannot found cgroup mount destination: unknown #219

xgenvn opened this issue Feb 5, 2018 · 149 comments

Comments

@xgenvn
Copy link

xgenvn commented Feb 5, 2018

  • This is a bug report
  • This is a feature request
  • I searched existing issues before opening this one

Expected behavior

docker run hello-world

should run normally.

Actual behavior

docker run hello-world
docker: Error response from daemon: cgroups: cannot found cgroup mount destination: unknown.

Steps to reproduce the behavior

Install latest stable or edge builds (17.12 or 18.01), using:
https://docs.docker.com/install/linux/docker-ce/ubuntu/

Output of docker version:

Client:                                    
 Version:       18.01.0-ce                 
 API version:   1.35                       
 Go version:    go1.9.2                    
 Git commit:    03596f5                    
 Built: Wed Jan 10 20:11:05 2018           
 OS/Arch:       linux/amd64                
 Experimental:  false                      
 Orchestrator:  swarm                      
                                           
Server:                                    
 Engine:                                   
  Version:      18.01.0-ce                 
  API version:  1.35 (minimum version 1.12)
  Go version:   go1.9.2                    
  Git commit:   03596f5                    
  Built:        Wed Jan 10 20:09:37 2018   
  OS/Arch:      linux/amd64                
  Experimental: false                      

Output of docker info:

Containers: 16                                                                    
 Running: 0                                                                       
 Paused: 0                                                                        
 Stopped: 16                                                                      
Images: 1                                                                         
Server Version: 18.01.0-ce                                                        
Storage Driver: overlay2                                                          
 Backing Filesystem: extfs                                                        
 Supports d_type: true                                                            
 Native Overlay Diff: true                                                        
Logging Driver: json-file                                                         
Cgroup Driver: cgroupfs                                                           
Plugins:                                                                          
 Volume: local                                                                    
 Network: bridge host macvlan null overlay                                        
 Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog    
Swarm: inactive                                                                   
Runtimes: runc                                                                    
Default Runtime: runc                                                             
Init Binary: docker-init                                                          
containerd version: 89623f28b87a6004d4b785663257362d1658a729                      
runc version: b2567b37d7b75eb4cf325b77297b140ea686ce8f                            
init version: 949e6fa                                                             
Security Options:                                                                 
 seccomp                                                                          
  Profile: default                                                                
Kernel Version: 4.4.0                                                             
Operating System: Ubuntu 16.04.3 LTS                                              
OSType: linux                                                                     
Architecture: x86_64                                                              
CPUs: 1                                                                           
Total Memory: 512MiB                                                              
Name: SRV_01                                                                      
ID: BBRL:P36V:7QOO:IRBR:X2TC:UC47:4L7N:IIIQ:OLSL:KWS2:OVAZ:TKKF                   
Docker Root Dir: /var/lib/docker                                                  
Debug Mode (client): false                                                        
Debug Mode (server): false                                                        
Registry: https://index.docker.io/v1/                                             
Labels:                                                                           
Experimental: false                                                               
Insecure Registries:                                                              
 127.0.0.0/8                                                                      
Live Restore Enabled: false                                                       
                                                                                  
WARNING: No cpuset support                                                        
WARNING: bridge-nf-call-iptables is disabled                                      
WARNING: bridge-nf-call-ip6tables is disabled                                     

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

> uname -a

Linux DAAA_S1 4.4.0 #1 SMP Fri Jan 5 21:20:16 MSK 2018 x86_64 x86_64 x86_64 GNU/Linux
> ls /sys/fs/cgroup/
beancounter  cpu          cpuacct  freezer  memory   net_cls,net_prio  perf_event  systemd
blkio        cpu,cpuacct  devices  hugetlb  net_cls  net_prio          pids        ve

AppArmor is also deactivated.
Running under root terminal/normal terminal returns same issue.
Docker pull is working.
Confirmed working under 17.09.1~ce-0~ubuntu

@AdrianAntunez
Copy link

AdrianAntunez commented Feb 13, 2018

Hi @xgenvn, have you fixed that issue? I'm at the same point but it occurs when docker is ran by a pipeline using gitlab ci/cd... Not sure if in my case it is a docker or a gitlab related issue

@xgenvn
Copy link
Author

xgenvn commented Feb 13, 2018

@AdrianAntunez I installed specific version: 17.09.1~ce-0~ubuntu and it's working fine now.

@AdrianAntunez
Copy link

@xgenvn I will give it a try ASAP and I will let you know if it worked for me or not. Thx!!

@philippbussche
Copy link

philippbussche commented Mar 17, 2018

@AdrianAntunez ran into the same issue, it is working with this configuration for me:

image: docker:17.09

services:
- docker:17.09-dind

@hectornevarez
Copy link

Same issue here, I'm running:

Version: 17.12.1-ce
API version: 1.35
Go version: go1.9.4
Git commit: 7390fc6
Built: Tue Feb 27 22:17:40 2018
OS/Arch: linux/amd64

@jkbaseer
Copy link

jkbaseer commented Mar 20, 2018

@philippbussche hey philip, so only the docker was a problem is it? Am also facing the same problem

My version

`Client:
Version: 17.12.0-ce
API version: 1.35
Go version: go1.9.2
Git commit: c97c6d6
Built: Wed Dec 27 20:03:51 2017
OS/Arch: darwin/amd64

Server:
Engine:
Version: 17.12.0-ce
API version: 1.35 (minimum version 1.12)
Go version: go1.9.2
Git commit: c97c6d6
Built: Wed Dec 27 20:12:29 2017
OS/Arch: linux/amd64
Experimental: true
`

For me Docker Hello World is working without a issue though.

@dinar-dalvi
Copy link

I ran into similar issue found a temp fix on another place.
Temp fix:
sudo mkdir /sys/fs/cgroup/systemd
sudo mount -t cgroup -o none,name=systemd cgroup /sys/fs/cgroup/systemd

@jkbaseer
Copy link

Hello @dinar-dalvi thanks a lot! Do i need to do this on the route directory of the Server? or in the app folder(for example: meteor/hello-app/

@xgenvn
Copy link
Author

xgenvn commented Mar 22, 2018

@dinar-dalvi I tried this before, however the systemd is existed and mounted. Downgrading seems to fix the issue.

@jkbaseer
Copy link

@xgenvn: downgrading the container to which version?

@xgenvn
Copy link
Author

xgenvn commented Mar 22, 2018

@jkbaseer you might want to try

sudo apt remove docker-ce
sudo apt install docker-ce=17.09.1~ce-0~ubuntu

@jkbaseer
Copy link

jkbaseer commented Mar 22, 2018

image
Am i doing it rightly?

(Ps: Also i have few containers am using for other project, will that be removed as well? or is there a single command only to downgrade? )

@d-a-v
Copy link

d-a-v commented Mar 28, 2018

On devuan/ascii this worked (over 18.03):

sudo apt-get install docker-ce=17.09.1~ce-0~debian

@xgenvn
Copy link
Author

xgenvn commented Mar 29, 2018

@jkbaseer no, I was speaking of Ubuntu command line, I'm not sure on Mac.

@jkbaseer
Copy link

jkbaseer commented Mar 29, 2018 via email

@AdrianAntunez
Copy link

In my case the runner was host in AWS, I tried everything and nothing worked so I decided to change the AMI (it's the virtual image which includes the SO). Swaping from amazon linux v1 to amazon linux v2 apparently solved my issue. Anyway I don't know why 😕

@vehsamrak
Copy link

I'm facing this too with Docker version 18.03.0-ce, build 0520e24
Solved by regressing to previous version of docker ce, as mentioned by @xgenvn

teancom added a commit to cloudfoundry-community/jumpbox-boshrelease that referenced this issue May 21, 2018
…ux#219, which breaks this release in bosh-lite

Signed-off-by: Steven Barry <[email protected]>
@lukkigi
Copy link

lukkigi commented Jun 3, 2018

I've just tried updating to the newest version again and it seems fixed for me in Docker version 18.03.1-ce, build 9ee9f40

@iwan933
Copy link

iwan933 commented Jun 21, 2018

Still facing this issue with 18.03.1~ce-0~ubuntu.

@notmessenger
Copy link

Ran into this as well running under root terminal/normal terminal and using 18.03.1-ce.
Confirmed works when downgrade to 17.09.1~ce-0~ubuntu

> docker version

Client:
 Version:      18.03.1-ce
 API version:  1.37
 Go version:   go1.9.5
 Git commit:   9ee9f40
 Built:        Thu Apr 26 07:17:20 2018
 OS/Arch:      linux/amd64
 Experimental: false
 Orchestrator: swarm

Server:
 Engine:
  Version:      18.03.1-ce
  API version:  1.37 (minimum version 1.12)
  Go version:   go1.9.5
  Git commit:   9ee9f40
  Built:        Thu Apr 26 07:15:30 2018
  OS/Arch:      linux/amd64
  Experimental: false
> docker info

Containers: 1
 Running: 0
 Paused: 0
 Stopped: 1
Images: 1
Server Version: 18.03.1-ce
Storage Driver: vfs
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 773c489c9c1b21a6d78b5c538cd395416ec50f88
runc version: 4fc53a81fb7c994640722ac585fa9ca548971871
init version: 949e6fa
Security Options:
 seccomp
  Profile: default
Kernel Version: 4.12.14-aufs
Operating System: Ubuntu 16.04 LTS (containerized)
OSType: linux
Architecture: x86_64
CPUs: 16
Total Memory: 62.88GiB
Name: antlet13
ID: KJZ3:L22I:HNCT:7O2X:VF6S:TRVG:ZCTT:IPR7:BHZR:AB6I:MYUY:KIBJ
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false

WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled
> uname -a

Linux antlet13 4.12.14-aufs #7 SMP Tue Jan 9 00:08:41 -00 2018 x86_64 x86_64 x86_64 GNU/Linux
> ls /sys/fs/cgroup/

blkio  cpu  cpuacct  cpu,cpuacct  cpuset  devices  freezer  hugetlb  memory  net_cls  net_cls,net_prio  perf_event  pids  systemd

@CpuID
Copy link

CpuID commented Jul 12, 2018

So basically, any image that expects systemd sysfs entries fails to start with this error correct, if you are running on a non-systemd based Linux system? Would others here concur with that statement?

@xgenvn
Copy link
Author

xgenvn commented Jul 16, 2018

@CpuID how do I know "the image expects systemd sysfs entries" ?

@CpuID
Copy link

CpuID commented Jul 16, 2018

@CpuID how do I know "the image expects systemd sysfs entries" ?

A difficult assumption to make ahead of time. The answer might need to be Docker passing through a mocked set of sysfs entries to the container sysfs, when the host OS doesn't have them (due to a lack of systemd)? Not 100% sure if thats wise, or might lead to more confusion... We hit the issue starting the official Elasticsearch Docker images, which I don't believe actually use systemd, but maybe they call something that expects systemd to be configured at least? shrug

@eedwards-sk
Copy link

got this during a docker-compose up for concourse's dev compose config, the concourse-db (postgres image), running inside docker-machine on a mac with virtualbox

it works again once I completely destroy the docker machine and re-create it

Creating network "local-concourse_default" with the default driver
Creating local-concourse_concourse-db_1 ...
Creating local-concourse_concourse-db_1 ... error

ERROR: for local-concourse_concourse-db_1  Cannot start service concourse-db: cgroups: cannot find cgroup mount destination: unknown

ERROR: for concourse-db  Cannot start service concourse-db: cgroups: cannot find cgroup mount destination: unknown
Encountered errors while bringing up the project.

docker version

Client:
 Version:           18.06.0-ce
 API version:       1.38
 Go version:        go1.10.3
 Git commit:        0ffa825
 Built:             Wed Jul 18 19:04:39 2018
 OS/Arch:           linux/amd64
 Experimental:      false

Server:
 Engine:
  Version:          18.06.0-ce
  API version:      1.38 (minimum version 1.12)
  Go version:       go1.10.3
  Git commit:       0ffa825
  Built:            Wed Jul 18 19:13:39 2018
  OS/Arch:          linux/amd64
  Experimental:     false

docker info

Containers: 2
 Running: 1
 Paused: 0
 Stopped: 1
Images: 3
Server Version: 18.06.0-ce
Storage Driver: aufs
 Root Dir: /mnt/sda1/var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 31
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: d64c661f1d51c48782c9cec8fda7604785f93587
runc version: 69663f0bd4b60df09991c08812a60108003fa340
init version: fec3683
Security Options:
 seccomp
  Profile: default
Kernel Version: 4.9.93-boot2docker
Operating System: Boot2Docker 18.06.0-ce (TCL 8.2.1); HEAD : 1f40eb2 - Thu Jul 19 18:48:09 UTC 2018
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 3.858GiB
Name: snap-dev
ID: S3SW:XQYT:MUTK:OZ45:HKRO:J65H:F6WE:BDR3:5TPD:YECG:QJDU:2GKZ
Docker Root Dir: /mnt/sda1/var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
 provider=virtualbox
Experimental: false
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false

ls /sys/fs/cgroup/

blkio/      cpuacct/    devices/    hugetlb/    net_cls/    perf_event/
cpu/        cpuset/     freezer/    memory/     net_prio/   pids/

uname -a

Linux snap-dev 4.9.93-boot2docker #1 SMP Thu Jul 19 18:29:50 UTC 2018 x86_64 GNU/Linux

@lenn4rd
Copy link

lenn4rd commented Aug 4, 2018

I too can confirm downgrading to 17.09.1~ce-0~ubuntu solves this issue for me. Every newer Docker CE version from the stable channel version produces the error message.

I'm running Docker inside an OpenVZ container (need to deal with it sadly) so this might contribute to the problem. The cgroup filesystems seem to be mounted but I don't trust a thing that this OpenVZ container says anymore.

I'm omitting information about the machine because it's close to what others have posted already, apart from the virtualisation maybe. Let me know if you need further information, I'll add it then.

@kgrodzicki
Copy link

We having the same issue with Docker version 18.03.1-ce running on AWS ECS with Concourse in docker.

@diggymo
Copy link

diggymo commented Sep 12, 2018

@kgrodzicki me too.

In ecs. Task(is mere DockerContainer) repeat starting and ending over many times.

the cause that Task stop is that CannotStartContainerError: API error (500): cgroups: cannot find cgroup mount destination: unknown

@flavienbwk
Copy link

I get this error on Ubuntu 22.04 with Docker version 19.03.15, build 99e3ed8919

@endigo
Copy link

endigo commented Jul 28, 2022

I get this error on Ubuntu 22.04 with Docker version 19.03.15, build 99e3ed8919

You need to install cgroup-tools.
https://installati.one/ubuntu/22.04/cgroup-tools/

@Pawel-Lukasik-Dev
Copy link

I needed to execute following commands to work for me. GL :)

sudo mkdir /sys/fs/cgroup/systemd
sudo mount -t cgroup -o none,name=systemd cgroup /sys/fs/cgroup/systemd

@Napsty
Copy link

Napsty commented Sep 20, 2022

subsequently upgrading Docker to version 20.10.8, it now supports cgroup2, and the "temp fix" is not needed.

Awesome hint, thank you @b01t !

Ran into this issue when I tried to run docker compose inside a Debian Buster LXC, the LXC host (physical server) was just upgraded from Buster to Bullseye before. The Buster LXC still had Docker 19.03 but after the upgrade to 20.10 docker compose worked again.

@jakk64
Copy link

jakk64 commented Sep 22, 2022

I needed to execute following commands to work for me. GL :)

sudo mkdir /sys/fs/cgroup/systemd sudo mount -t cgroup -o none,name=systemd cgroup /sys/fs/cgroup/systemd

Thank you. It has worked after upgrading Ubuntu 20.04 LTS to 22.04 LTS

@juannyG
Copy link

juannyG commented Oct 13, 2022

sudo mkdir /sys/fs/cgroup/systemd
sudo mount -t cgroup -o none,name=systemd cgroup /sys/fs/cgroup/systemd

I followed these steps but it ended up breaking my snap such that

  • applications installed via snap would not run
  • snap install X would not work

Instead, I uninstalled docker-ce & re-installed docker-ce, using these steps: https://www.digitalocean.com/community/tutorials/how-to-install-and-use-docker-on-ubuntu-22-04 and all my docker & snaps worked fine.

@melekabbassi
Copy link

I ran into similar issue found a temp fix on another place. Temp fix: sudo mkdir /sys/fs/cgroup/systemd sudo mount -t cgroup -o none,name=systemd cgroup /sys/fs/cgroup/systemd

Thank you!!

esatterwhite added a commit to esatterwhite/semantic-release-docker that referenced this issue Dec 19, 2022
downgrade the ubuntu version in effort to get the old cgroups mounts
back for CI. There seems to be a problem with the new version on
ubuntu-latest.

See: systemd/systemd#13477
See: docker/for-linux#219
@nikos445
Copy link

Almost same problem was occured to my jenkins pipelines after upgrading from Ubuntu Server 21.04 to 22.04.

The solution that worked for me was to disable the cgroup_hierarchy from grub boot.
Note: I am using containerd and runc instead of docker but this may work also in docker

Solution Commands:

echo "GRUB_CMDLINE_LINUX=systemd.unified_cgroup_hierarchy=false" | sudo tee /etc/default/grub.d/cgroup.cfg
sudo update-grub

Previously mentioned solution did not work... it was displaying that mounts was already mounted

sudo mkdir -p /sys/fs/cgroup/systemd
sudo mount -t cgroup -o none,name=systemd cgroup /sys/fs/cgroup/systemd

@leni1
Copy link

leni1 commented Jan 9, 2023

Instead, I uninstalled docker-ce & re-installed docker-ce, using these steps: https://www.digitalocean.com/community/tutorials/how-to-install-and-use-docker-on-ubuntu-22-04 and all my docker & snaps worked fine.

Had an issue related to this and a re-install of docker worked for me on KDE Neon 5.24 (which uses Ubuntu 22.04 as a base)

@Lupunita
Copy link

In cgroups v2 - By default, a non-root user can only get memory controller and pids controller to be delegated.

I resolved this by following steps from https://rootlesscontaine.rs/getting-started/common/cgroup2/#enabling-cpu-cpuset-and-io-delegation

@TheMessik
Copy link

Same issue here with GitLab CI/CD - can be fixed by using the same version for dind image as on host.

test-debian11-docker-dind:
  image: docker:20.10.12
  services:
    - name: docker:20.10.12-dind

Has anyone managed to resolve this?

@drpaneas
Copy link

drpaneas commented Apr 4, 2023

I encountered this as well ...

@nutellatux
Copy link

Almost same problem was occured to my jenkins pipelines after upgrading from Ubuntu Server 21.04 to 22.04.

The solution that worked for me was to disable the cgroup_hierarchy from grub boot. Note: I am using containerd and runc instead of docker but this may work also in docker

Solution Commands:

echo "GRUB_CMDLINE_LINUX=systemd.unified_cgroup_hierarchy=false" | sudo tee /etc/default/grub.d/cgroup.cfg
sudo update-grub

Previously mentioned solution did not work... it was displaying that mounts was already mounted

sudo mkdir -p /sys/fs/cgroup/systemd
sudo mount -t cgroup -o none,name=systemd cgroup /sys/fs/cgroup/systemd

OS: "Ubuntu 22.04.2 LTS" its fixed!!!! TKS!!!!!!!!!!!!

  1. sudo apt-get update
  2. sudo apt-get -y install cgroup-tools
  3. sudo mkdir /sys/fs/cgroup/systemd
  4. sudo mount -t cgroup -o none,name=systemd cgroup /sys/fs/cgroup/systemd
  5. echo "GRUB_CMDLINE_LINUX=systemd.unified_cgroup_hierarchy=false" | sudo tee /etc/default/grub.d/cgroup.cfg
  6. sudo update-grub

@renepavlik
Copy link

I just faced this after upgrading a debian stretch machine to bullseye. The trick with

sudo mkdir /sys/fs/cgroup/systemd
sudo mount -t cgroup -o none,name=systemd cgroup /sys/fs/cgroup/systemd

worked for me, but it was a bad lead.

The root of the problem was elsewhere, in the fact, that docker-ce (and related) package was staying on the old version built for stretch. This means it works on bullseye but uses cgroups v1 while in bullseye, there is cgroups2.

The real resolution was to upgrade docker-ce to the bullseye version.

@Sieboldianus
Copy link

Thanks @renepavlik . I can confirm, updating docker solved this problem for me under Debian bullseye. Here's the link to how to do this, just follow https://docs.docker.com/engine/install/debian/#install-using-the-repository.

@magnusja
Copy link

Hi, there I had the same error after upgrading from Ubuntu 21.04 to 21.10. On each dist upgrade, libraries on your computer are being disabled. With the help of my Ubuntu expert colleague @MVermue we solved it.

My error:

ERROR: for xxxdocker_mysql_1  Cannot start service mysql: cgroups: cgroup mountpoint does not exist: unknown

Solution: package got disabled on upgrade, we need to manually overlook them and fix

Problem situation:

* After upgrade from every ubuntu version, you need to do the following checks:
/etc/apt/sources.list.d
ls -lah

Now you see a list, like the following

...
ansible-ubuntu-ansible-focal.list
ansible-ubuntu-ansible-focal.list.distUpgrade
ansible-ubuntu-ansible-focal.save
docker.list
docker.list.distUpgrade
docker.list.save
mysql.list
mysql.list.distUpgrade
mysql.list.save
...

Step 1:

We need to edit the files which end on ".list", f.e.: sudo vim docker.list Check the URL in the file, click on it, check if "dist" folder exists (and make sure you see Release, so you know it has been released) and the latest OS system you are on. In my case, it should be "impish".

Changed from

# deb [arch=amd64] https://download.docker.com/linux/ubuntu disco stable

New content

deb [arch=amd64] https://download.docker.com/linux/ubuntu impish stable

Step 2

Take a peek at the content of the .distUpgrade file.

cat docker.list.distUpgrade

If all lines are commented, you can remove the file with sudo rm docker.list.distUpgrade. (If there are lines not commented. They must be in the .list file, then you can remove the distUpgrade.)

Step 3

Repeat step 1 and 2 for all .list/.distUpgrade files in this folder.

Step 4

Repeat step 1 and 2 in the folder /etc/apt/.

Step 5

sudo apt update
sudo apt upgrade

Finished and fixed. Now all your tools are up-to-date.

OMG thank you so much! This should be the highlighted solution!

@greatquux
Copy link

@magnusja this is definitely helpful, however these are steps everyone should take after an Ubuntu upgrade if they have added any PPAs to their system. for safety during the upgrade they get disabled, and these steps should be taken to re-enable them afterwards. this can help get the latest package versions installed for the new Ubuntu you have upgraded to. there are other reasons why this message may come up however, so it's not necessarily the solution for everyone, but is good general advice nonetheless.

@magnusja
Copy link

magnusja commented Dec 1, 2023

@magnusja this is definitely helpful, however these are steps everyone should take after an Ubuntu upgrade if they have added any PPAs to their system. for safety during the upgrade they get disabled, and these steps should be taken to re-enable them afterwards. this can help get the latest package versions installed for the new Ubuntu you have upgraded to. there are other reasons why this message may come up however, so it's not necessarily the solution for everyone, but is good general advice nonetheless.

I mean if Ubuntu is not able to provide a working Docker package in their own repos, then certainly using Docker official PPA is the way to go. I agree that you probably should think about if you want to activate other PPAs as well. But people also added the PPA back in the days for a reason.

pitkley added a commit to pitkley/dfw that referenced this issue Dec 19, 2023
Ubuntu 22.04 upgrades systemd, which upgrades how cgroups are handled, which
the old Docker versions are not happy with.

See:
- docker/for-linux#219
- systemd/systemd#13477
@adebisi-fa
Copy link

adebisi-fa commented Apr 18, 2024

I ran into similar issue found a temp fix on another place. Temp fix: sudo mkdir /sys/fs/cgroup/systemd sudo mount -t cgroup -o none,name=systemd cgroup /sys/fs/cgroup/systemd

This worked for me, in 2024. Thank YOU @dinar-dalvi!!

SERVER:
Ubuntu 22.04.

Client: Docker Engine - Community
Version: 26.0.1
API version: 1.40 (downgraded from 1.45)
Go version: go1.21.9
Git commit: d260a54
Built: Thu Apr 11 10:53:25 2024
OS/Arch: linux/amd64
Context: default

Server: Docker Engine - Community
Engine:
Version: 19.03.12
API version: 1.40 (minimum version 1.12)
Go version: go1.13.10
Git commit: 48a66213fe
Built: Mon Jun 22 15:44:17 2020
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.2.13
GitCommit: 7ad184331fa3e55e52b890ea95e65ba581ae3429
runc:
Version: 1.0.0-rc10
GitCommit: dc9208a3303feef5b3839f4323d9beb36df0a9dd
docker-init:
Version: 0.18.0
GitCommit: fec3683

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests