Designs that are relevant to desktop containers.
Docker for Windows
- Provides access to Docker through the command line
- Sign into a Docker cloud account
- Switch between Windows or Linux containers
- Status information shows when Docker is/isn’t running
- Settings window allows configuration of:
- Which drives are shared with containers
- Hardware resources that are made available to Docker
- Network settings
- Create and view containers
- Run/stop/restart containers
- Configure filesystem access to containers
- Open a terminal for a container
Eclipse Docker Integration
Functionality (seems to do most of what you can do with the Docker CLI):
- Create and manage connections to Docker daemons
- Start/stop containers
- View images and containers
- Search the Docker registry for images
- Configure all the things…
- Very popular before containers (it uses VMs)
- Allows development environments to be deployed and shared. Each environment is defined using a VagrantFile and a provisioning framework, such as Puppet.
- Pre-built environments are called boxes. There’s a catalogue of them, and they can be used as bases or templates on which to base your own.
- It’s possible to configure some other aspects of boxes, like their networking settings.
- Vagrant will also sync the project with a location on the host, so it’s possible to work there.
- Terminals that are specific to containers
- Allows creating new projects from templates
- Shows the Git context
- Could show the status of production images?
- CoreOS toolbox (documentation)
- Jonathan’s homebrew effort
- Colin’s homebrew effort
Each of these use a single privileged container as a place to install CLI development tools. These can be debugging tools like tcpdump and strace. They can also be administration/automation tools like ansible, oc, aws.
The container has to be privileged, so that it has access to other containers.
- Visual studio docker integration
- Python virtual environments
- Powerline, a fancy bash prompt