-
Notifications
You must be signed in to change notification settings - Fork 85
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
Comments
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 |
@AdrianAntunez I installed specific version: |
@xgenvn I will give it a try ASAP and I will let you know if it worked for me or not. Thx!! |
@AdrianAntunez ran into the same issue, it is working with this configuration for me: image: docker:17.09 services: |
Same issue here, I'm running: Version: 17.12.1-ce |
@philippbussche hey philip, so only the docker was a problem is it? Am also facing the same problem My version `Client: Server: For me Docker Hello World is working without a issue though. |
I ran into similar issue found a temp fix on another place. |
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/ |
@dinar-dalvi I tried this before, however the systemd is existed and mounted. Downgrading seems to fix the issue. |
@xgenvn: downgrading the container to which version? |
@jkbaseer you might want to try
|
On devuan/ascii this worked (over 18.03):
|
@jkbaseer no, I was speaking of Ubuntu command line, I'm not sure on Mac. |
Hey Guys,
Sorry I gave up of this trying even after installing latest Ubuntu ce. just created a new VM and used my container. And the app is back thankfully :)
It took so much to solve this Cpgroup. Appreciate all your help!
… On 29 Mar 2018, at 9:23 am, Anh Tu Nguyen ***@***.***> wrote:
@jkbaseer no, I was speaking of Ubuntu command line, I'm not sure on Mac.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
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 😕 |
I'm facing this too with |
…ux#219, which breaks this release in bosh-lite Signed-off-by: Steven Barry <[email protected]>
I've just tried updating to the newest version again and it seems fixed for me in |
Still facing this issue with |
Ran into this as well running under root terminal/normal terminal and using > 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 |
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? |
@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 |
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
docker version
docker info
ls /sys/fs/cgroup/
uname -a
|
I too can confirm downgrading to 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. |
We having the same issue with Docker version 18.03.1-ce running on AWS ECS with Concourse in docker. |
@kgrodzicki me too. In ecs. Task(is mere DockerContainer) repeat starting and ending over many times. the cause that Task stop is that |
I get this error on Ubuntu 22.04 with Docker version 19.03.15, build 99e3ed8919 |
You need to install |
I needed to execute following commands to work for me. GL :)
|
Awesome hint, thank you @b01t ! Ran into this issue when I tried to run |
Thank you. It has worked after upgrading Ubuntu 20.04 LTS to 22.04 LTS |
I followed these steps but it ended up breaking my
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. |
Thank you!! |
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
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. Solution Commands:
Previously mentioned solution did not work... it was displaying that mounts was already mounted
|
Had an issue related to this and a re-install of |
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 |
Has anyone managed to resolve this? |
I encountered this as well ... |
OS: "Ubuntu 22.04.2 LTS" its fixed!!!! TKS!!!!!!!!!!!!
|
I just faced this after upgrading a debian stretch machine to bullseye. The trick with
worked for me, but it was a bad lead. The root of the problem was elsewhere, in the fact, that The real resolution was to upgrade |
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. |
OMG thank you so much! This should be the highlighted solution! |
@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. |
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
This worked for me, in 2024. Thank YOU @dinar-dalvi!! SERVER: Client: Docker Engine - Community Server: Docker Engine - Community |
Expected behavior
should run normally.
Actual behavior
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
:Output of
docker info
:Additional environment details (AWS, VirtualBox, physical, etc.)
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
The text was updated successfully, but these errors were encountered: