FS#49582 - [docker] Failed to load due to undefined flags with 1:1.11.2

Attached to Project: Community Packages
Opened by Bin Jin (bjin) - Monday, 06 June 2016, 00:01 GMT
Last edited by Ike Devolder (BlackEagle) - Monday, 06 June 2016, 12:39 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sébastien Luttringer (seblu)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 22
Private No

Details

Description:

I failed to restart docker daemon today after a package upgrade (to 1:1.11.2), with the following error message in journal.


time="2016-06-06T01:56:20.208575737+02:00" level=info msg="New containerd process, pid: 4705\n"
Incorrect Usage.
NAME:
containerd - High performance container daemon
USAGE:
docker-containerd [global options] command [command options] [arguments...]

VERSION:
0.1.0 commit: 7e3c007ea30b938561921d0318bc91b7087fbe7d

COMMANDS:
help, h Shows a list of commands or help for one command

GLOBAL OPTIONS:
--debug enable debug output in the logs
--state-dir "/run/containerd" runtime state directory
--metrics-interval "5m0s" interval for flushing metrics to the store
--listen, -l "/run/containerd/containerd.sock" Address on which GRPC API will listen
--runtime, -r "runc" name of the OCI compliant runtime to use when executing containers
--graphite-address Address of graphite server
--help, -h show help
--version, -v print the version

time="2016-06-06T01:56:20+02:00" level=fatal msg="flag provided but not defined: -start-timeout"



Steps to reproduce:
1. Upgrade to docker 1:1.11.2
2. sudo systemctl daemon-reload
3. sudo systemctl restart docker
This task depends upon

Closed by  Ike Devolder (BlackEagle)
Monday, 06 June 2016, 12:39 GMT
Reason for closing:  Fixed
Additional comments about closing:  updated both containerd and runc to the last versions 0.2.2 and 0.1.1
Comment by Bin Jin (bjin) - Monday, 06 June 2016, 00:03 GMT
A downgrade to 1:1.11.1-1 fixes the problem.
Comment by Tansin Watabato (neverwinter) - Monday, 06 June 2016, 01:51 GMT
Can confirm this has happened to me also. Reverting package to version docker-1:1.11.1-1-x86_64.pkg.tar.xz resolved the issue for me.
Comment by Nikolay (develnk) - Monday, 06 June 2016, 04:18 GMT
I have this problem too.
Comment by Vladyslav Frolov (frol) - Monday, 06 June 2016, 05:17 GMT
There are a number of reports on Docker github issue-tracker:

* https://github.com/docker/docker/issues/23289
* https://github.com/docker/docker/issues/23288

It seems that all of the affected people are using Arch Linux.
Comment by Alexander (SIDS) - Monday, 06 June 2016, 07:23 GMT
Same issue.
Comment by Andreas Pieber (pieber) - Monday, 06 June 2016, 09:25 GMT
Same issue - manually upgrading containerd as sugggested here https://github.com/docker/docker/issues/23289 also did the trick.
Comment by Aleksi Johansson (aleksijohansson) - Monday, 06 June 2016, 10:26 GMT
Same issue here.
Comment by Aleksi Johansson (aleksijohansson) - Monday, 06 June 2016, 11:08 GMT
Manually upgrading containerd as suggested here https://github.com/docker/docker/issues/23289 also worked for me!
Comment by Ike Devolder (BlackEagle) - Monday, 06 June 2016, 12:38 GMT
updated containerd and runc in the repo's

Loading...