I will attempt to expand more on each of these as I learn the different phases of dockerization.
CoreOS Docker Quirks
Command-Line Completion: Unsupported
Bash completion is not available for CoreOS, making it difficult or impossible to install docker command completion, as described here: https://docs.docker.com/compose/completion/
Installing Docker Compose
Since the /usr/local/bin/ folder is read-only, and sudo -i did not seem to help, I was able to install docker-compose by using curl to place the executable in my home folder (or any writable folder). Then, executing `export PATH=$PATH:/path/to/docker/compose`
Debugging
Building a Container
- docker stats <name or id> - shows memory usage / limits
- docker run <id> - can use the id of incremental build images to boot into the failing state
Running a Container
- docker events <id> - shows what docker daemon is doing in the background
- docker inspect <name or id> - inspect a particular container's configuration
- docker logs <id> - shows the logs of a particular container
- nsenter - enter a particular namespace
Inspecting a Running Container
- docker exec -it <name or id> /bin/bash