Bug 1399981

Summary:	docker-storage-setup.service loaded failed failed
Product:	[Fedora] Fedora	Reporter:	techtonik
Component:	docker-storage-setup	Assignee:	Andy Grimm <agrimm>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	25	CC:	agrimm, hobbes1069
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-12 10:08:35 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description techtonik 2016-11-30 07:38:30 UTC

Description of problem:

This docker service does not start:

$ sudo systemctl status docker-storage-setup
● docker-storage-setup.service - Docker Storage Setup
   Loaded: loaded (/usr/lib/systemd/system/docker-storage-setup.service; disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Wed 2016-11-30 10:23:16 +03; 7min ago
  Process: 5820 ExecStart=/usr/bin/docker-storage-setup (code=exited, status=1/FAILURE)
 Main PID: 5820 (code=exited, status=1/FAILURE)

Nov 30 10:23:16 blackbox systemd[1]: Starting Docker Storage Setup...
Nov 30 10:23:16 blackbox docker-storage-setup[5820]: ERROR: Docker has been previously configured for use with devicemapper graph driver. Not creating a new thin pool as existing docker metadata will fail to work with it. Manual cleanup is required before this will succeed.
Nov 30 10:23:16 blackbox docker-storage-setup[5820]: INFO: Docker state can be reset by stopping docker and by removing /var/lib/docker directory. This will destroy existing docker images and containers and all the docker metadata.
Nov 30 10:23:16 blackbox systemd[1]: docker-storage-setup.service: Main process exited, code=exited, status=1/FAILURE
Nov 30 10:23:16 blackbox systemd[1]: Failed to start Docker Storage Setup.
Nov 30 10:23:16 blackbox systemd[1]: docker-storage-setup.service: Unit entered failed state.
Nov 30 10:23:16 blackbox systemd[1]: docker-storage-setup.service: Failed with result 'exit-code'.

$ sudo systemctl stop docker
$ sudo rm -rf /var/lib/docker
$ sudo systemctl status docker-storage-setup
● docker-storage-setup.service - Docker Storage Setup
   Loaded: loaded (/usr/lib/systemd/system/docker-storage-setup.service; disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Wed 2016-11-30 10:35:11 +03; 16s ago
  Process: 6637 ExecStart=/usr/bin/docker-storage-setup (code=exited, status=5)
 Main PID: 6637 (code=exited, status=5)

Nov 30 10:35:11 blackbox systemd[1]: Starting Docker Storage Setup...
Nov 30 10:35:11 blackbox docker-storage-setup[6637]:   Rounding up size to full physical extent 32,00 MiB
Nov 30 10:35:11 blackbox docker-storage-setup[6637]:   Volume group "fedora" has insufficient free space (0 extents): 8 required.
Nov 30 10:35:11 blackbox systemd[1]: docker-storage-setup.service: Main process exited, code=exited, status=5/NOTINSTALLED
Nov 30 10:35:11 blackbox systemd[1]: Failed to start Docker Storage Setup.
Nov 30 10:35:11 blackbox systemd[1]: docker-storage-setup.service: Unit entered failed state.
Nov 30 10:35:11 blackbox systemd[1]: docker-storage-setup.service: Failed with result 'exit-code'.

$ df -h
Filesystem               Size  Used Avail Use% Mounted on
devtmpfs                 3.9G     0  3.9G   0% /dev
tmpfs                    3.9G  126M  3.8G   4% /dev/shm
tmpfs                    3.9G  1.7M  3.9G   1% /run
tmpfs                    3.9G     0  3.9G   0% /sys/fs/cgroup
/dev/mapper/fedora-root   21G   14G  6.5G  67% /
tmpfs                    3.9G  124K  3.9G   1% /tmp
/dev/sda3                477M  140M  308M  32% /boot
/dev/sda5                 30G   26G  2.5G  92% /home
tmpfs                    788M   16K  788M   1% /run/user/42
tmpfs                    788M  5.8M  783M   1% /run/user/1000


Version-Release number of selected component (if applicable):
docker.x86_64                           2:1.12.3-9.git47e22f2.fc25 @updates     
docker-common.x86_64                    2:1.12.3-9.git47e22f2.fc25 @updates

Comment 1 Richard Shaw 2017-08-11 18:35:15 UTC

Also seeing this on my F25 system, I have not modified the default configuration.

Comment 2 Fedora End Of Life 2017-11-16 19:40:01 UTC

This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2017-12-12 10:08:35 UTC

Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.