Kubespray: Avoid using both flags and /etc/docker/daemon.json

Created on 26 Jul 2017  路  7Comments  路  Source: kubernetes-sigs/kubespray

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
Bug Report

Environment:

  • *Cloud provider or hardware configuration: * CentOS 7 bare metal

docker[7988]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives are specified both as a flag and in the

lifecyclrotten

Most helpful comment

Got the same issue on debian bare metal.

It seams my previous installation of docker is conflucting with installation of kubespray. I delete the file /etc/docker/daemon.json to fix the issue.

All 7 comments

Got the same issue on debian bare metal.

It seams my previous installation of docker is conflucting with installation of kubespray. I delete the file /etc/docker/daemon.json to fix the issue.

/etc/systemd/system/docker.service.d/* should use least options as possible,and other configurations should be used in /etc/docker/daemon.json ,such as insecure-registries, storage-driver,storage-opts,live-restore,oom-score-adjust,debug ...

Hello,
Fresh CentOS 7.4 install.
Just installed docker with "yum install docker" (got 2:1.13.1-53.git774336d.el7.centos).

File "/usr/lib/systemd/system/docker.service" contains:
EnvironmentFile=-/etc/sysconfig/docker-storage
called line 25:
$DOCKER_STORAGE_OPTIONS \
which contains:
DOCKER_STORAGE_OPTIONS="--storage-driver overlay2 "

Removed content of file /etc/sysconfig/docker-storage and could start docker without problem using devmapper as specified in /etc/docker/daemon.json

WIP for fixing this with #4286

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Was this page helpful?
0 / 5 - 0 ratings