Instructions fail for making the docker engine listen on a tcp port (as well as a unix socket)

[akc42]

File: engine/admin/systemd.md

I have an installation on a raspberry pi (using raspbian jessie), and am trying to follow instructions to make the docker engine listen on a tcp port (as well as a unix socket). As this section suggests, I created the /etc/docker/daemon.json file and added a "hosts": ["tcp://0.0.0.0:4243", "unix:///var/run/docker.sock"] entry. However, this approach fails with a message that says that there is an entry in the config file trying to override the flags passed to the daemon on startup. I think this is because /lib/systemd/system/docker.service starts the service with the the flag -H fd://

It is not clear the correct approach here, but the documentation just doesn't match. I am worried that editing /lib/systemd/system/docker.service to remove the flags will just get overwritten on the next upgrade. Perhaps the debian package should provide a small daemon.json file rather than provide flags on the start

[noncreature0714]

Checking this out! @johndmulhausen @mstanleyjones @londoncalling

[londoncalling]

@noncreature0714 adding hackathon labels for you.

[noncreature0714]

This is taking me a while to work through, I'm going to have to take this home tonight so I can connect to my own network.

[noncreature0714]

Still working through this! It's a tad more time consuming that I expected.

[mdlinville]

Any luck, @noncreature0714 ? Let me know if you are not ready to submit a PR for this one and I'll remove it from the Hackathon milestone. You can feel free to keep working through it, though!

[noncreature0714]

@mstanleyjones I'm still working on it, but I've been super busy! I'll dedicate time to it this afternoon! I'd like to see it through.

[noncreature0714]

@mstanleyjones I re-read your comment - I'm not ready to submit a PR at this time, sorry that wasn't clear! I hope to submit one tonight, but I'm aware that's probably after the Hackathon is over!