boo2docker should provide a way to set daemon flags

[proppy]

Either throught flag or configuration, it'd be nice to have a way to mess with the daemon flags without ssh'ing into the VM and restarting the daemon.

That'd esp. be handy with the new --insecure-registry flag to allow running registry on localhost.

Related:
moby/moby#8887
moby/moby#8889
moby/moby#8898

[tianon]

To add flags to the daemon, you need to add EXTRA_ARGS="--daemon --flags --here" to your /var/lib/boot2docker/profile and then things should "just work" (IIRC).

[proppy]

@tianon yes, but it's not that easy to add that 'from the outside', you have to ssh and restart.

I'd be cool if boot2docker-cli was doing some magic here (not sure yet how).

[dekz]

Is there a way to forward the boot2docker profile into the VM using shared folders? Or is that entirely too environment specific.

I foresee this isn't a large problem for those using the public repositories or private repositories with https.

Creating /var/lib/boot2docker/profile and populating EXTRA_ARGS="--insecure-registry..." did the trick for me.

[CleanCut]

@proppy @dekz @tianon This affects me as well.

[CleanCut]

After lots of research around here I found I was able to use this as a temporary workaround (I have to run it every time I start boot2docker):

boot2docker ssh 'sudo sh -c "echo \"EXTRA_ARGS=\\\"--insecure-registry 10.0.0.0/8\\\"\" > /var/lib/boot2docker/profile && sudo /etc/init.d/docker restart"'

[sscarduzio]

+1

[SQiShER]

+1 - it would be nice if the EXTRA_ARGS would somehow survive boot2docker upgrades.

[danielbryantuk]

+1 to @CleanCut's solution. Many thanks!

[CleanCut]

@daniel-bryant-uk Glad it could help someone! I'm still mystified as to why boot2docker and docker seem to be content to leave this in such a user-unfriendly state!

[daghack]

@CleanCut Because boot2docker-cli is officially pending deprecation as of #334.

[CleanCut]

@Moghedrin Whaaaat??? boot2docker itself is going away? This is news to me!

To summarize for the others in this thread who also don't know, boot2docker is being mothballed. Everyone is being redirected to use the (apparently new) official docker "machine" project here.

Man, every time I think I get something figured out with respect to docker, it changes out from under me.

[danielbryantuk]

Wow - yeah, I have been keenly following Docker machine, but didn't realise that it would deprecate boot2docker...

I suppose this does make sense, but I don't think this is being communicated enough to the community

[daghack]

@CleanCut It is going away, but nobody should be being redirected yet, as Docker Machine is still in its early stages. While boot2docker-cli is pending deprecation, it's still the official solution to use.

[CleanCut]

@Moghedrin Thanks for the clarification. It appears they've only ever had two official alpha releases so far. It looks like an ambitious project, though. Are boot2docker devs moving over there to help out as well?

[daghack]

@CleanCut If the maintainers want to contribute there, then nothing is stopping them - open source ftw! Outside of that, I don't know, and it seems rather early to be making guesses.

[sscarduzio]

+1

[tianon]

Sorry, this repository is long-since deprecated in favor of Docker Toolbox (whose usage is now also discouraged in favor of Docker for Windows and Docker for Mac).