-
Notifications
You must be signed in to change notification settings - Fork 265
swarm-vagrant-manager.json writes to /etc/default/docker which does not work on systemd systems #325
Comments
Hi! In systemd, docker daemon option is define
|
@YujiOshima Thank you for the response. I had tried using /etc/docker/daemon.json but was unsuccessful. I assume, as you mention, it was being overridden. I tried using your "Init" example above to update
When I ran through the startup, it still did not work.
I am invoking |
Don't all of these in
|
@dougbeauchene
Init commands in vagrant instance plugin are vagrant Shell Provisioner script (boot.sh). I refactor the commands, it's worked for me.
|
I replaced my
I started all of the plugins, each in their own terminal session using these commands...
I started the manager node...
In the shell where I started the
When I check on the contents of
When I try to list the swarm nodes, it fails to connect to the daemon...
As I mentioned in my post yesterday, when I ran the commands manually that are in Any advice you can offer would be appreciated. Thanks |
@dougbeauchene |
I added the
When I try to list node...
The docker config file does not appear to be updated...
|
In case it is helpful to you to see the logs from a somewhat successful (manual) series of steps, I'm providing the following. I reset my enviornment. I started the plug-ins like above, with logging. I ran these commands from
then I went ahead and ran this command...
The plugin-in log output is...
|
I am trying to deploy Infrakit in a Ubuntu 16.04 vm running via VirtualBox on my Windows laptop.
I'm running into an issue that when I try to fire up the swarm-vagrant-workers using...
src/github.com/docker/infrakit/build/infrakit group commit src/github.com/docker/infrakit/pkg/example/flavor/swarm/swarm-vagrant-workers.json
I believe the root issue is the docker daemon cannot be reached.
In
swarm-vagrant-manager.json
I see/etc/default/docker
being updated withDOCKER_OPTS
...But according to what I'm reading (moby/moby#25357),
/etc/default/docker
is only used on systems running upstart and sysvinit, not on systems using systemd like Ubuntu 16.04 which I'm using.So the setting of
DOCKER_OPTS
and the restart of docker inswarm-vagrant-manager.json
aren't going to work for me.Does this seem like a likely source of why I can't get Infrakit stood up and talking to the docker daemon?
The text was updated successfully, but these errors were encountered: