I want the ability for a designer to select "file open" and then select the docker-compose.yml file to "launch" our stack.
Without that, it seems like you still need to rely on the docker-cli to build images from a Dockerfile.
I want the ability for a designer to select "file open" and then select the docker-compose.yml file to "launch" our stack.
Without that, it seems like you still need to rely on the docker-cli to build images from a Dockerfile.
Has it gotten better, is there a trick you're using, or am I hitting an edge case you don't have?
We haven't had a problem since the Docker 1.3 update.
VirtualBox filesystem performance isn't amazing, but it isn't anywhere near that bad. There was probably another issue involved here.
My first job was at a call center where we trained literally anyone who applied to use command line DOS to take orders for sausage over the phone. This took three days to teach these people how to navigate a pretty extensive CLI interface. Many of them were highschool dropouts with GEDs. If they even attempted to use the mouse the computer would lock up. We had virtually zero issues.
It's astonishing that some people refuse to even open a terminal.
Kitematic could abstract that layer (boot2docker) away with a GUI.