Whoa!
It's still failing with the re-spinned 4.8.0-42-generic kernel.
But this time I can see more error message from systemctl status output, which
is complaining about the driver this time.
(Test case: ubuntu_fan_smoke_test)
# systemctl status docker.service
docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; disabled; vendor preset:
enabled)
Drop-In: /etc/systemd/system/docker.service.d
[email protected]
Active: failed (Result: start-limit-hit) since Thu 2017-03-09 23:42:04 EST;
2min 7s ago
Docs: https://docs.docker.com
Process: 3482 ExecStart=/usr/bin/dockerd -H fd:// $DOCKER_OPTS (code=exited,
status=1/FAILURE)
Main PID: 3482 (code=exited, status=1/FAILURE)
Mar 09 23:42:03 kernel02 dockerd[3482]:
time="2017-03-09T23:42:03.315347000-05:00" level=info msg="libcontainerd: new
containerd process, pid: 3501"
Mar 09 23:42:04 kernel02 dockerd[3482]:
time="2017-03-09T23:42:04.370521000-05:00" level=error msg="[graphdriver] prior
storage driver \"aufs\" failed: driver not supported"
Mar 09 23:42:04 kernel02 dockerd[3482]:
time="2017-03-09T23:42:04.370569000-05:00" level=fatal msg="Error starting
daemon: error initializing graphdriver: driver not supported"
Mar 09 23:42:04 kernel02 systemd[1]: docker.service: Main process exited,
code=exited, status=1/FAILURE
Mar 09 23:42:04 kernel02 systemd[1]: Failed to start Docker Application
Container Engine.
Mar 09 23:42:04 kernel02 systemd[1]: docker.service: Unit entered failed state.
Mar 09 23:42:04 kernel02 systemd[1]: docker.service: Failed with result
'exit-code'.
Mar 09 23:42:04 kernel02 systemd[1]: docker.service: Start request repeated too
quickly.
Mar 09 23:42:04 kernel02 systemd[1]: Failed to start Docker Application
Container Engine.
Mar 09 23:42:04 kernel02 systemd[1]: docker.service: Failed with result
'start-limit-hit'.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1671058
Title:
docker service failed to start on s390x (zVM) Yakkety
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Yakkety:
Triaged
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/system/docker.service; disabled; vendor
preset: enabled)
Drop-In: /etc/systemd/system/docker.service.d
└─http-proxy.conf
Active: failed (Result: start-limit-hit) since Wed 2017-03-08 06:06:54
EST; 14min ago
Docs: https://docs.docker.com
Process: 3752 ExecStart=/usr/bin/dockerd -H fd:// $DOCKER_OPTS
(code=exited, status=1/FAILURE)
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.service/start/replace
Mar 08 06:06:54 kernel02 systemd[1]: docker.service: Installed new job
docker.service/start as 1897
Mar 08 06:06:54 kernel02 systemd[1]: docker.service: Enqueued job
docker.service/start as 1897
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.service/start
finished, result=failed
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-0ubuntu1~16.10.1
ProcVersionSignature: Ubuntu 4.8.0-40.43-generic 4.8.17
Uname: Linux 4.8.0-40-generic s390x
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
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)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671058/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
