Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#41159 - [docker] 1:1.1.0.1 fails to start with "package not installed"

Attached to Project: Community Packages
Opened by Michael Xavier (michaelxavier) - Thursday, 10 July 2014, 15:48 GMT
Last edited by Sébastien Luttringer (seblu) - Wednesday, 16 July 2014, 13:38 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sébastien Luttringer (seblu)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

All of my packages are updated to the latest. After attempting to start docker, nothing happened and the process was not started. Looking at the status I see:

● docker.service - Docker Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled)
Active: failed (Result: start-limit) since Thu 2014-07-10 08:35:21 PDT; 10min ago
Docs: http://docs.docker.com
Process: 19736 ExecStart=/usr/bin/docker -d (code=exited, status=1/FAILURE)
Main PID: 19736 (code=exited, status=1/FAILURE)

Jul 10 08:35:21 Apollo-Beta systemd[1]: Unit docker.service entered failed state.
Jul 10 08:35:21 Apollo-Beta systemd[1]: docker.service holdoff time over, scheduling restart.
Jul 10 08:35:21 Apollo-Beta systemd[1]: Stopping Docker Application Container Engine...
Jul 10 08:35:21 Apollo-Beta systemd[1]: Starting Docker Application Container Engine...
Jul 10 08:35:21 Apollo-Beta systemd[1]: docker.service start request repeated too quickly, refusing to start.
Jul 10 08:35:21 Apollo-Beta systemd[1]: Failed to start Docker Application Container Engine.
Jul 10 08:35:21 Apollo-Beta systemd[1]: Unit docker.service entered failed state.

When attempting to run the daemonized command manually I see:

$ sudo /usr/bin/docker -d

[f5fab8e1] +job serveapi(unix:///var/run/docker.sock)
[f5fab8e1] +job initserver()
[f5fab8e1.initserver()] Creating server
2014/07/10 08:46:50 Listening for HTTP on unix (/var/run/docker.sock)
[f5fab8e1] +job init_networkdriver()
[f5fab8e1.init_networkdriver()] creating new bridge for docker0
package not installed
[f5fab8e1] -job init_networkdriver() = ERR (1)
package not installed
[f5fab8e1] -job initserver() = ERR (1)
2014/07/10 08:46:50 package not installed

Please do let me know if there's more detail I could report.

Steps to reproduce:
1. Install docker
2. run systemctl start docker
This task depends upon

Closed by  Sébastien Luttringer (seblu)
Wednesday, 16 July 2014, 13:38 GMT
Reason for closing:  Not a bug
Comment by Michael Xavier (michaelxavier) - Sunday, 13 July 2014, 21:26 GMT
I'm not sure if this is valid. It looks like I needed the bridge module enabled. This problem went away after a reboot. Not sure if the package could do anything about that. Please close if it can't.
Comment by Sébastien Luttringer (seblu) - Wednesday, 16 July 2014, 13:38 GMT
Drop a file into /etc/modules-load.d/ to load bridge module. That should do the job.

Loading...