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

containerd: container not started on docker 1.12.3 #347

Closed
uzytkownik opened this issue Nov 8, 2016 · 2 comments
Closed

containerd: container not started on docker 1.12.3 #347

uzytkownik opened this issue Nov 8, 2016 · 2 comments

Comments

@uzytkownik
Copy link

uzytkownik commented Nov 8, 2016

I run into problem on Gentoo.

Docker version:

Client:
 Version:      1.12.3
 API version:  1.24
 Go version:   go1.7.3
 Git commit:   6b644ec
 Built:        
 OS/Arch:      linux/amd64

Server:
 Version:      1.12.3
 API version:  1.24
 Go version:   go1.7.3
 Git commit:   6b644ec
 Built:        
 OS/Arch:      linux/amd64
-----
Containers: 6
 Running: 2
 Paused: 0
 Stopped: 4
Images: 140
Server Version: 1.12.3
Storage Driver: btrfs
 Build Version: Btrfs v4.8.1
 Library Version: 101
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: null bridge host overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: seccomp
Kernel Version: 4.8.6-gentoo-efi
Operating System: Gentoo/Linux
OSType: linux
Architecture: x86_64
CPUs: 12
Total Memory: 15.68 GiB
Name: mpiechotka-dt-l
ID: HFZX:DCEA:E4OF:FGMM:YCVW:COZT:LISW:L4MH:FHLR:6OIP:FESN:BZ3P
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 27
 Goroutines: 50
 System Time: 2016-11-08T13:17:28.974134684-08:00
 EventsListeners: 0
Registry: https://index.docker.io/v1/
Insecure Registries:
 127.0.0.0/8
@uzytkownik
Copy link
Author

It looks like problem was due to incorrect option ordering. It might be good to have better error messages.

@fabiorauber
Copy link

Container not started on docker exec:
rpc error: code = 2 desc = containerd: container not started

Terrible error message. Made me think the original container was not running. Turns out the container did not have bash installed.

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

2 participants