bootstrap with multinode does not deploy docker

[Carlos Letamendía]

Bootstrap-servers runs okay, prechecks run okay, then deploy fails because of the need for a docker registry. There is no mention on the quickstart guide regarding manual installation of docker/the registry.

When following the specific multinode guide, if one follwos all the steps and installs docker, the registries, etc and then bootstraps, the way bootstrap-servers implements the config conflicts/breaks the way suggested by the guide (using the systemd file instead of the daemon.json, which causes it to break if doing both)

[Mark Goddard (mgoddard)]

Thanks for the bug report Carlos. Bootstrap servers will install the docker daemon. It will not install a registry - you might prefer to just use dockerhub, but even if you do want a private registry you would not install it on all of your hosts.

I'm finding it a bit difficult to work out what the problem is, could you give a set of steps to reproduce it, and outline what you expect to see vs. what you actually see. Thanks

[Carlos Letamendía (ohwhyosa)]

When following this guide: https://docs.openstack.org/kolla-ansible/rocky/user/multinode.html
The second section, "Configure Docker on all nodes", configures the "insecure registries" option via /etc/docker/daemon.json (which, as far as I know, is the recommended docker way to do it).

The bootstrap-servers command configures the same option via the systemd unit ExecStart command (--insecure-registries flag).

Even though there is no mention of the command bootstrap-servers in said multinode guide, if one executes it (for it to take care of the rest of the bootstrapping tasks) after enabling the insecure registries via daemon.json, the docker daemon crashes (more details at https://docs.docker.com/config/daemon/#troubleshoot-conflicts-between-the-daemonjson-and-startup-scripts)