Docker can't start s390x images on Ubuntu and gets "oci runtime error: unrecognized architecture"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu on IBM z Systems |
Fix Released
|
Undecided
|
Unassigned | ||
runc (Ubuntu) |
Fix Released
|
Critical
|
Skipper Bug Screeners | ||
Xenial |
Fix Released
|
High
|
Unassigned | ||
Yakkety |
Fix Released
|
High
|
Unassigned | ||
Zesty |
Fix Released
|
Critical
|
Skipper Bug Screeners |
Bug Description
[Impact]
* Regression in updates
* Cannot start a docker container on s390x/ppc64el
[Test Case]
* $ sudo docker run -t s390x/ubuntu
Should start a container without an error on s390x
* $ sudo docker run -t ppc64le/ubuntu
Should start a container without an error on ppc64el
[Regression Potential]
* Minimal, the fix is a cherrypick of vendorised update of seccomp sub-library which now includes architecture defines to/from native arch and s390x/ppc64el.
[Other Info]
Starting different s390x Docker images on Ubuntu 16.04.1 (and 16.10) fails:
#######
Problem description:
# docker run s390x/ubuntu
Unable to find image 's390x/
latest: Pulling from s390x/ubuntu
b43bc799d4e2: Pull complete
afbd2b8f99bf: Pull complete
0e3aee0ec255: Pull complete
eb19a6534950: Pull complete
29583cd8abac: Pull complete
Digest: sha256:
Status: Downloaded newer image for s390x/ubuntu:latest
docker: Error response from daemon: oci runtime error: unrecognized architecture.
# docker run s390x/busybox
...
..
docker: Error response from daemon: oci runtime error: unrecognized architecture.
#######
System description:
# uname -a
Linux s8330034 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:05:09 UTC 2016 s390x s390x s390x GNU/Linux
# docker info
Containers: 2
Running: 0
Paused: 0
Stopped: 2
Images: 2
Server Version: 1.12.3
Storage Driver: aufs
Root Dir: /var/lib/
Backing Filesystem: extfs
Dirs: 10
Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: overlay bridge null host
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: apparmor seccomp
Kernel Version: 4.4.0-36-generic
Operating System: Ubuntu 16.04.1 LTS
OSType: linux
Architecture: s390x
CPUs: 1
Total Memory: 860.4 MiB
Name: s8330034
ID: XWPX:2EKT:
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https:/
WARNING: No swap limit support
Insecure Registries:
127.0.0.0/8
# docker version
Client:
Version: 1.12.3
API version: 1.24
Go version: go1.6.2
Git commit: 6b644ec
Built: Mon, 19 Dec 2016 09:20:48 +1300
OS/Arch: linux/s390x
Server:
Version: 1.12.3
API version: 1.24
Go version: go1.6.2
Git commit: 6b644ec
Built: Mon, 19 Dec 2016 09:20:48 +1300
OS/Arch: linux/s390x
tags: | added: architecture-s39064 bugnameltc-150822 severity-high targetmilestone-inin16041 |
Changed in ubuntu: | |
assignee: | nobody → Skipper Bug Screeners (skipper-screen-team) |
affects: | ubuntu → docker (Ubuntu) |
Changed in docker (Ubuntu): | |
status: | New → Confirmed |
Changed in ubuntu-z-systems: | |
status: | New → Confirmed |
tags: | added: regression-update s390x |
Changed in docker (Ubuntu): | |
importance: | Undecided → Critical |
affects: | docker (Ubuntu) → docker.io (Ubuntu) |
Changed in docker.io (Ubuntu Xenial): | |
status: | New → Fix Committed |
Changed in docker.io (Ubuntu Yakkety): | |
status: | New → Triaged |
Changed in docker.io (Ubuntu Zesty): | |
status: | Confirmed → Triaged |
Changed in ubuntu-z-systems: | |
status: | Confirmed → Fix Committed |
Changed in ubuntu-z-systems: | |
status: | Fix Committed → Triaged |
Changed in ubuntu-z-systems: | |
status: | Triaged → Fix Committed |
Changed in ubuntu-z-systems: | |
status: | Fix Committed → Fix Released |
Changed in runc (Ubuntu Xenial): | |
importance: | Undecided → High |
Changed in runc (Ubuntu Yakkety): | |
importance: | Undecided → High |
tags: | added: universe |
I was able to recreate this problem ... (only with 1.12.3, not with 1.12.1)