kops does not use DOCKER_OPTS or /etc/sysconfig/docker in docker.service

[imsky]

i'm using kops 1.5 to tweak the storage driver on a cluster and while /etc/sysconfig/docker receives the correct flags, docker.service does not use that file as an EnvironmentFile and does not append $DOCKER_OPTS to the main command. this leads to dockerd using devicemapper as the storage driver.

[chrislovecnm]

What would you expect?

[imsky]

i'd expect that the DOCKER_OPTS are set in the systemd docker service so that changing the storage driver in kops cluster settings actually has an effect

[justinsb]

This is fixed in kops 1.5.0, which should release today.

For example, I set:

  docker:
    storage: overlay2

and docker was run with /usr/bin/dockerd --ip-masq=false --iptables=false --log-level=warn --storage-driver=overlay2

(note this is only an example, as overlay2 is not officially supported with k8s 1.5)

Closing; please reopen if not fixed in 1.5.0.

[imsky]

@justinsb unfortunately this is not fixed. the systemd service file is correctly generated and the docker version is set correctly, but the storage driver still defaults to devicemapper. restarting the docker service via systemd fixes the issue, but this is something kops should do already.

[justinsb]

Ouch - sorry @imsky

Can you confirm the AMI you are running & the kops version please?

Edit, from slack: "we're on 1.5.1, ami is k8s-1.4-debian-jessie-amd64-hvm-ebs-2016-10-21 (ami-4bb3e05c)"

[justinsb]

I think #2102 will fix it @imsky - see the comment for an explanation.

As a simple workaround, if you update the AMI to 1.5, it should "just work". kops upgrade cluster should recommend an image upgrade, I believe; you can either apply it manually or accept its recommendations (it'll probably recommend a k8s upgrade also though).