Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docker drop in service for flannel setup incorrect #349

Open
urkle opened this issue Aug 7, 2016 · 5 comments
Open

Docker drop in service for flannel setup incorrect #349

urkle opened this issue Aug 7, 2016 · 5 comments

Comments

@urkle
Copy link

urkle commented Aug 7, 2016

The documentation on http://www.projectatomic.io/docs/gettingstarted/ mentioned to add a "drop-in" for systemd to override docker.. However the example file is incorrect and yields the following error when startup up docker.

Aug 07 23:05:45 atomic01.kaos.realm systemd[1]: docker.service has more than one ExecStart= setting, which is only allowed for Type=oneshot services. Refusing.

There was an open bug up on the docker github that references how to fix this issue.

moby/moby#14491

The solution is simply to ADD an

ExecStart=

before the full ExecStart= line. I've tested this locally and it does indeed work as expected.

@urkle
Copy link
Author

urkle commented Aug 8, 2016

Actually this "drop-in" is no longer needed in current CentOS7 atomic host. the stock setup auto picks up flannel setup.

Also, the documentation needs to mention that the edits /etc/sysconf/flanneld needs to happen on the atomic-master as well!

@jberkus
Copy link
Contributor

jberkus commented Aug 9, 2016

I'm a little unclear on all of the corrections needed? Can you break them out?

@urkle
Copy link
Author

urkle commented Aug 9, 2016

@jberkus yeah.. sure. I was reporting these as I was figuring out how to get an atomic setup in VMs and after getting past one hurdle hit another one, but now it's all working.

First this is based on using the latest CentOS 7 Atomic Host.

  • the "drop-in" flanneld service is not needed (that is the /etc/systemd/system/docker.service.d/10-flanneld-network.conf file). Just simply configuring the /etc/sysconfig/flanneld and renabling the flanneld service is enough to have docker service pickup the flannel configuration.
    • this obviates my original note about ExecStart=
  • the documentation needs to mention in the section about editing /etc/sysconfig/flanneld to ALSO change that file and enable the service on the master!

@nzwulfin
Copy link
Contributor

nzwulfin commented Aug 9, 2016

All of this points to the fact that the doc hasn't been retooled in a while and was based on Fedora 22 Atomic Host. An earlier version of this doc did have the ExecStart= line in the drop-in and the usage is still described in the text.

Since there may be material differences between the CentOS and Fedora Atomic Hosts at any point in time, should look to split the doc or have call outs for differences?

@urkle
Copy link
Author

urkle commented Aug 9, 2016

I can try and go through the doc on a F24 later this week and see how it differs from CentOS7.. If there are minimal (or no differences) then the call-outs seems the better option.. If there are significant differences then the split approach would be better.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants