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

Unable to run container on Ubuntu "Error response from daemon: Cannot start container ...: operation not supported" #7246

Closed
nazar-pc opened this Issue Jul 25, 2014 · 10 comments

Comments

Projects
None yet
6 participants
@nazar-pc

nazar-pc commented Jul 25, 2014

When running container I get instant error:

nazar-pc@nazar-pc:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu Utopic Unicorn (development branch)
Release:    14.10
Codename:   utopic
nazar-pc@nazar-pc:~$ uname -a
Linux nazar-pc 3.16.0-rc6-haswell #1 SMP Mon Jul 21 08:08:55 EEST 2014 x86_64 x86_64 x86_64 GNU/Linux
nazar-pc@nazar-pc:~$ docker version
Client version: 1.1.2
Client API version: 1.13
Go version (client): go1.2.1
Git commit (client): d84a070
Server version: 1.1.2
Server API version: 1.13
Go version (server): go1.2.1
Git commit (server): d84a070
nazar-pc@nazar-pc:~$ docker run -t -i ubuntu:14.04 /bin/bash
2014/07/25 15:37:25 Error response from daemon: Cannot start container 9a92fdcaef51612a384922729a4ebd72289795553f506d365d95fa588e43010b: operation not supported

I have custom kernel, but I do not see anything that can point me to the reason why it doesn't work.
I do not see anything in system logs, and there are no logs specially for Docker.

@nazar-pc

This comment has been minimized.

Show comment
Hide comment
@nazar-pc

nazar-pc Aug 2, 2014

One week issue, does anyone know what this can be, how to show more detail about this issue?

nazar-pc commented Aug 2, 2014

One week issue, does anyone know what this can be, how to show more detail about this issue?

@nazar-pc

This comment has been minimized.

Show comment
Hide comment
@nazar-pc

nazar-pc Aug 2, 2014

Thanks to #4627 I fixed problem by:

  • adding VETH support in my custom kernel
  • installing lxc and cgroup-lite

nazar-pc commented Aug 2, 2014

Thanks to #4627 I fixed problem by:

  • adding VETH support in my custom kernel
  • installing lxc and cgroup-lite

@nazar-pc nazar-pc closed this Aug 2, 2014

@lsabban

This comment has been minimized.

Show comment
Hide comment
@lsabban

lsabban Nov 2, 2014

Hello
I have the same error on RedHat 6.6
I have installed Docker using EPEL and docker.io

[root@mydtbld0035g ~]# docker version
Client version: 1.1.2
Client API version: 1.13
Go version (client): go1.2.2
Git commit (client): d84a070/1.1.2
2014/11/02 13:22:17 GET /v1.13/version
[b0aedbdb] +job version()
[b0aedbdb] -job version() = OK (0)
Server version: 1.1.2
Server API version: 1.13
Go version (server): go1.2.2
Git commit (server): d84a070/1.1.2

[root@mydtbld0035g ~]# uname -a
Linux mydtbld0035g.isr.hp.com 2.6.32-279.el6.x86_64 #1 SMP Wed Jun 13 18:24:36 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux

When I run "docker run -ti ubuntu /bin/bash"

I get

[b0aedbdb] +job create()
[b0aedbdb] -job create() = OK (0)
2014/11/02 11:13:39 POST /v1.13/containers/8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8/attach?stderr=1&stdin=1&stdout=1&stream=1
[b0aedbdb] +job container_inspect(8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8)
[b0aedbdb] -job container_inspect(8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8) = OK (0)
[b0aedbdb] +job attach(8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8)
2014/11/02 11:13:39 POST /v1.13/containers/8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8/start
[b0aedbdb] +job start(8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8)
[b0aedbdb] +job allocate_interface(8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8)
[b0aedbdb] -job allocate_interface(8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8) = OK (0)
[error] container.go:475 Error running container: write /cgroup/devices/docker/8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8/cgroup.procs: invalid argument
[b0aedbdb] +job release_interface(8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8)
[b0aedbdb] -job release_interface(8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8) = OK (0)
[error] container.go:522 8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8: Error closing terminal: invalid argument
[b0aedbdb] -job attach(8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8) = OK (0)
[b0aedbdb] +job release_interface(8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8)
[b0aedbdb] -job release_interface(8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8) = OK (0)
[error] container.go:522 8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8: Error closing terminal: invalid argument
[error] driver.go:140 Warning: error unmounting device 8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8: UnmountDevice: device not-mounted id 8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8

Cannot start container 8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8: write /cgroup/devices/docker/8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8/cgroup.procs: invalid argument
[b0aedbdb] -job start(8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8) = ERR (1)
[error] server.go:1048 Error making handler: Cannot start container 8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8: write /cgroup/devices/docker/8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8/cgroup.procs: invalid argument
[error] server.go:90 HTTP Error: statusCode=500 Cannot start container 8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8: write /cgroup/devices/docker/8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8/cgroup.procs: invalid argument
2014/11/02 11:13:40 Error response from daemon: Cannot start container 8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8: write /cgroup/devices/docker/8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8/cgroup.procs: invalid argument

Could anyone please suggest resolution?
I tried to upgrade lxc and cgroups but they are already at their latest.

Thanks

lsabban commented Nov 2, 2014

Hello
I have the same error on RedHat 6.6
I have installed Docker using EPEL and docker.io

[root@mydtbld0035g ~]# docker version
Client version: 1.1.2
Client API version: 1.13
Go version (client): go1.2.2
Git commit (client): d84a070/1.1.2
2014/11/02 13:22:17 GET /v1.13/version
[b0aedbdb] +job version()
[b0aedbdb] -job version() = OK (0)
Server version: 1.1.2
Server API version: 1.13
Go version (server): go1.2.2
Git commit (server): d84a070/1.1.2

[root@mydtbld0035g ~]# uname -a
Linux mydtbld0035g.isr.hp.com 2.6.32-279.el6.x86_64 #1 SMP Wed Jun 13 18:24:36 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux

When I run "docker run -ti ubuntu /bin/bash"

I get

[b0aedbdb] +job create()
[b0aedbdb] -job create() = OK (0)
2014/11/02 11:13:39 POST /v1.13/containers/8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8/attach?stderr=1&stdin=1&stdout=1&stream=1
[b0aedbdb] +job container_inspect(8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8)
[b0aedbdb] -job container_inspect(8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8) = OK (0)
[b0aedbdb] +job attach(8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8)
2014/11/02 11:13:39 POST /v1.13/containers/8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8/start
[b0aedbdb] +job start(8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8)
[b0aedbdb] +job allocate_interface(8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8)
[b0aedbdb] -job allocate_interface(8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8) = OK (0)
[error] container.go:475 Error running container: write /cgroup/devices/docker/8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8/cgroup.procs: invalid argument
[b0aedbdb] +job release_interface(8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8)
[b0aedbdb] -job release_interface(8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8) = OK (0)
[error] container.go:522 8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8: Error closing terminal: invalid argument
[b0aedbdb] -job attach(8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8) = OK (0)
[b0aedbdb] +job release_interface(8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8)
[b0aedbdb] -job release_interface(8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8) = OK (0)
[error] container.go:522 8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8: Error closing terminal: invalid argument
[error] driver.go:140 Warning: error unmounting device 8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8: UnmountDevice: device not-mounted id 8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8

Cannot start container 8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8: write /cgroup/devices/docker/8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8/cgroup.procs: invalid argument
[b0aedbdb] -job start(8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8) = ERR (1)
[error] server.go:1048 Error making handler: Cannot start container 8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8: write /cgroup/devices/docker/8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8/cgroup.procs: invalid argument
[error] server.go:90 HTTP Error: statusCode=500 Cannot start container 8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8: write /cgroup/devices/docker/8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8/cgroup.procs: invalid argument
2014/11/02 11:13:40 Error response from daemon: Cannot start container 8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8: write /cgroup/devices/docker/8ea5f6db6273033700f107d8dd96fd430c1d77469d288a8ad01f70e78fecbaa8/cgroup.procs: invalid argument

Could anyone please suggest resolution?
I tried to upgrade lxc and cgroups but they are already at their latest.

Thanks

@nazar-pc

This comment has been minimized.

Show comment
Hide comment
@nazar-pc

nazar-pc Nov 2, 2014

Do you have custom kernel? I had custom kernel, and as stated in previous comment enabling one option and rebuiding helped me.

nazar-pc commented Nov 2, 2014

Do you have custom kernel? I had custom kernel, and as stated in previous comment enabling one option and rebuiding helped me.

@lsabban

This comment has been minimized.

Show comment
Hide comment
@lsabban

lsabban Nov 2, 2014

Could you please state the commands for that? I have no idea if I have custom kernel...
[root@mydtbld0035g ~]# uname -a
Linux mydtbld0035g.isr.hp.com 2.6.32-279.el6.x86_64 #1 SMP Wed Jun 13 18:24:36 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux

lsabban commented Nov 2, 2014

Could you please state the commands for that? I have no idea if I have custom kernel...
[root@mydtbld0035g ~]# uname -a
Linux mydtbld0035g.isr.hp.com 2.6.32-279.el6.x86_64 #1 SMP Wed Jun 13 18:24:36 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux

@nazar-pc

This comment has been minimized.

Show comment
Hide comment
@nazar-pc

nazar-pc Nov 2, 2014

Yes, you have non-standart Ubuntu kernel.
As I wrote previously I've enabled VETH option in kernel config and rebuild it, if you have no idea how to do that - try to ask who give you this server, they should know (also, I'm not sure you have exacly the same problem, maybe you'll need some other options in kernel).

nazar-pc commented Nov 2, 2014

Yes, you have non-standart Ubuntu kernel.
As I wrote previously I've enabled VETH option in kernel config and rebuild it, if you have no idea how to do that - try to ask who give you this server, they should know (also, I'm not sure you have exacly the same problem, maybe you'll need some other options in kernel).

@pkufergus

This comment has been minimized.

Show comment
Hide comment
@pkufergus

pkufergus Nov 6, 2014

I also meet this situation in CentOS7. then i restart the docker. it will ok.

pkufergus commented Nov 6, 2014

I also meet this situation in CentOS7. then i restart the docker. it will ok.

@mhdali

This comment has been minimized.

Show comment
Hide comment
@mhdali

mhdali Sep 1, 2015

I run into this issue today after I updated my Kernel, I'm using Arch.

Restarting docker didn't help, only reboot helped.

I'm not sure if this is the right solution, but it was my laptop so reboot is not a big deal comparing to real life production servers.

there is could be another solution that no need to reboot your OS, but I'm too lazy to check it out :)

mhdali commented Sep 1, 2015

I run into this issue today after I updated my Kernel, I'm using Arch.

Restarting docker didn't help, only reboot helped.

I'm not sure if this is the right solution, but it was my laptop so reboot is not a big deal comparing to real life production servers.

there is could be another solution that no need to reboot your OS, but I'm too lazy to check it out :)

@tlipinski

This comment has been minimized.

Show comment
Hide comment
@tlipinski

tlipinski Nov 5, 2015

Contributor

@mhdali: Same here - reboot fixed it after kernel update in Arch :)

Contributor

tlipinski commented Nov 5, 2015

@mhdali: Same here - reboot fixed it after kernel update in Arch :)

@zjy666666

This comment has been minimized.

Show comment
Hide comment
@zjy666666

zjy666666 commented Mar 23, 2018

help

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment