docker service failed to start on s390x (zVM) Yakkety
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
High
|
Unassigned | ||
Yakkety |
Won't Fix
|
High
|
Unassigned |
Bug Description
docker.service failed to start on s390x(zVM) Yakkety 4.8.0-40-generic proposed kernel
# systemctl status docker.service
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/
Drop-In: /etc/systemd/
Active: failed (Result: start-limit-hit) since Wed 2017-03-08 06:06:54 EST; 14min ago
Docs: https:/
Process: 3752 ExecStart=
Main PID: 3752 (code=exited, status=1/FAILURE)
Mar 08 06:06:54 kernel02 systemd[1]: docker.service: Unit entered failed state.
Mar 08 06:06:54 kernel02 systemd[1]: docker.service: Failed with result 'exit-code'.
Mar 08 06:06:54 kernel02 systemd[1]: docker.service: cgroup is empty
Mar 08 06:06:54 kernel02 systemd[1]: docker.service: Trying to enqueue job docker.
Mar 08 06:06:54 kernel02 systemd[1]: docker.service: Installed new job docker.
Mar 08 06:06:54 kernel02 systemd[1]: docker.service: Enqueued job docker.
Mar 08 06:06:54 kernel02 systemd[1]: docker.service: Start request repeated too quickly.
Mar 08 06:06:54 kernel02 systemd[1]: docker.service: Job docker.
Mar 08 06:06:54 kernel02 systemd[1]: Failed to start Docker Application Container Engine.
Mar 08 06:06:54 kernel02 systemd[1]: docker.service: Failed with result 'start-limit-hit'.
Please find attachment for partial log from journalctl -xe
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: docker.io 1.12.6-
ProcVersionSign
Uname: Linux 4.8.0-40-generic s390x
NonfreeKernelMo
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: s390x
Date: Wed Mar 8 06:17:52 2017
SourcePackage: docker.io
UpgradeStatus: No upgrade log present (probably fresh install)
It looks like this is a regression, I switched back to 4.8.0-38, and docker service can be started without any problem.