jdost/den

CLI tool for managing docker-based development environments

den's Issues

Image management

Add in a subcommand group for image management. This would probably be based around building iterative docker commands along the lines of Start up container for target image > Allow user to make changes to image > Have docker convert container into image with same tag > Teardown container. But there will probably be some options for how it is tagged, likely via the command line.

Also some local image support (local image being a Dockerfile in the local directory). Maybe have a default support for something like a Dockerfile.den that is specific to being used with den?

Use more of the docker API over `subprocess` calls

Right now, almost all interactions with the docker daemon are done via wrapped shell calls. The docker API is imported and available and should be used where possible. Starting with image creation and then experimenting with attachment via the API instead of the command line (may not be viable here as it may not tie stdin/stdout correctly).

Expand information command set

Right now the only information command is list which is pretty thin in definition. This can be moved into a command set for information that includes other options like listing images, getting information for running containers, etc. These would probably need to be simple in nature as too much information is crazy (just use the docker commands if you want to know everything, den is meant to obfuscate this interface only).

Files created inside of a `den` have root ownership

Because of the bind-mount, any files created via commands in the den will be owned by UID 0 (i.e. root). Fixing this is not straightforward, so it is caused by underlying kernel systems. There may not be a solution for it, but it is not a great behavior.