rapids-compose assumes docker daemon is running even though it just installed it.

[harrism]

ERROR: Couldn't connect to Docker daemon at http+docker://localhost - is it running?

If it's at a non-standard location, specify the URL with the DOCKER_HOST environment variable.
Makefile:139: recipe for target 'dc' failed
make[3]: *** [dc] Error 1
Makefile:108: recipe for target 'dc.up' failed
make[2]: *** [dc.up] Error 2
Makefile:94: recipe for target 'dc.apt.cacher.up' failed
make[1]: *** [dc.apt.cacher.up] Error 2
Makefile:36: recipe for target 'rapids.build' failed
make: *** [rapids.build] Error 2

If you run make init on a new Ubuntu install, rapids-compose will install Docker. But then when you run make, Docker daemon won't be running.

It would be nice for the compose instructions to show how to run the daemon, or to run it itself after installing.

[trxcllnt]

hm... it should have printed a reminder to reboot after make init finishes.

I don't think there's a way to run docker immediately as your non-root user without rebooting or logging out/logging back in, since your user has to be in the docker group.

[harrism]

You are correct. Make works after reboot. I don't think there was a reminder to reboot. Even this tutorial doesn't tell you to reboot after installing docker: https://www.digitalocean.com/community/tutorials/how-to-install-and-use-docker-on-ubuntu-18-04