-
Notifications
You must be signed in to change notification settings - Fork 120
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
Comments
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! |
I'm a little unclear on all of the corrections needed? Can you break them out? |
@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.
|
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 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? |
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. |
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.
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
before the full ExecStart= line. I've tested this locally and it does indeed work as expected.
The text was updated successfully, but these errors were encountered: