Bug 1217613 - Cannot start container [8] System error: mountpoint for cpuset not found
Summary: Cannot start container [8] System error: mountpoint for cpuset not found
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: cockpit
Version: 21
Hardware: armv7l
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Dominik Perpeet
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-30 19:59 UTC by Jirka Folta
Modified: 2021-12-29 10:04 UTC (History)
17 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-02 19:48:19 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
screenshot of the error (95.07 KB, image/png)
2015-04-30 19:59 UTC, Jirka Folta
no flags Details

Description Jirka Folta 2015-04-30 19:59:42 UTC
Created attachment 1020711 [details]
screenshot of the error

Description of problem:
when trying to run a container using Cockpit I get "System error: mountpoint for cpuset not found" error  

Version-Release number of selected component (if applicable):
cockpit:
 Version 0.27.
Built on Wed Mar 25 12:53:20 UTC 2015. 


How reproducible:
allways

Steps to Reproduce:
1.Install minimal Fedora 21 for arm platform from
http://www.digitaldreamtime.co.uk/images/Fidora/21/
2.update the system
3.install cockpit and docker
4.login to the server using web interface https://ip:9090
5.download Image: docker.io/wordpress:latest
6. try running the image

Actual results:
you get an error message(attached)


Expected results:
actually running the image

Additional info:

Comment 1 Jirka Folta 2015-04-30 20:10:26 UTC
[root@fidora-minimal-remix ~]# docker info
Containers: 1
Images: 33
Storage Driver: devicemapper
 Pool Name: docker-179:3-127068-pool
 Pool Blocksize: 65.54 kB
 Backing Filesystem: extfs
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 934.5 MB
 Data Space Total: 107.4 GB
 Data Space Available: 28.01 GB
 Metadata Space Used: 2.003 MB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.145 GB
 Udev Sync Supported: true
 Data loop file: /var/lib/docker/devicemapper/devicemapper/data
 Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
 Library Version: 1.02.93 (2015-01-30)
Execution Driver: native-0.2
Kernel Version: 3.18.12-501.20150429git2747cc0.sc20.armv7hl.bcm2709
Operating System: Fedora 21 (Twenty One)
CPUs: 4
Total Memory: 974.7 MiB
Name: fidora-minimal-remix
ID: 5UQ7:IPRF:NNL4:QMQQ:IVQU:QEPE:HHYH:WA75:LURE:4US5:LA6J:IULE
WARNING: No memory limit support
WARNING: No swap limit support
[root@fidora-minimal-remix ~]# sudo docker version
Client version: 1.6.0
Client API version: 1.18
Go version (client): go1.4.2
Git commit (client): 3eac457/1.6.0
OS/Arch (client): linux/arm
Server version: 1.6.0
Server API version: 1.18
Go version (server): go1.4.2
Git commit (server): 3eac457/1.6.0
OS/Arch (server): linux/arm




[root@fidora-minimal-remix ~]#  cat /proc/cgroups 
#subsys_name	hierarchy	num_cgroups	enabled
cpu	2	51	1
cpuacct	2	51	1
memory	0	1	0
devices	3	51	1
freezer	4	5	1
net_cls	5	1	1
blkio	6	51	1





[root@fidora-minimal-remix ~]# cat /etc/redhat-release 
Fedora release 21 (Twenty One)

Comment 2 Jan Chaloupka 2015-05-01 09:34:54 UTC
Hi Jirka,

it looks like cgroups are not mounted for docker. This is more like cockpit issue.

Can you run ls /sys/fs/cgroup/ on the f21 machine and inside docker?

Jan

Comment 3 Jirka Folta 2015-05-03 15:26:20 UTC
Hey, Jan
here you go:

[root@fidora-minimal-remix ~]# ls /sys/fs/cgroup/
blkio  cpu  cpuacct  cpu,cpuacct  devices  freezer  net_cls  systemd

Comment 4 Jan Chaloupka 2015-05-04 09:45:35 UTC
Thanks Jirka.

This looks like cockpit is running docker without mounted cgroups.

Comment 5 Dominik Perpeet 2015-05-04 13:57:46 UTC
Hi Jirka,

have you tried running the docker command manually in the shell for comparison (not in cockpit)? e.g. "docker run docker.io/wordpress:latest"

As far as I know we don't access cpuset from inside cockpit and we only interface with a running docker instance. If docker isn't running we offer to start it for the user, which is internally done via "systemctl start docker".

If it works in the console and not in cockpit, could you also please test running a simple container like busybox via cockpit?

Dominik

Comment 6 Fedora End Of Life 2015-11-04 12:10:53 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 7 Jan Kurik 2015-12-02 19:48:26 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 8 Jirka Folta 2021-12-29 10:04:09 UTC
still receiving emails from this, I can see that this is closed, what is the best way to stop the email notifications coming?


Note You need to log in before you can comment on or make changes to this bug.