Skip to main content
Jump to: navigation, search

Linux Tools Project/Docker Tooling/User Guide

< Linux Tools Project‎ | Docker Tooling
Revision as of 21:46, 10 December 2015 by (Talk | contribs) (Run Image)


The Linux Tools Docker Tooling plug-ins allow a user to manage Docker Images and Containers with similar functionality found in the command-line docker command.

For details on Docker and the docker command, see the Docker web-site at

Docker Tooling Perspective

A new perspective known as the Docker Tooling Perspective is added.


This perspective brings up three new views added:

In addition, the Docker Tooling Perspective adds the Console View and the Properties View.

The Console View is used to display logs of stdout/stderr output from Containers and in some instances, allow input to stdin. The Properties View allows clicking on various elements such as Connections, Images, and Containers and getting detailed info not readily shown in the various views mentioned above.

For example, clicking on a connection shows the following:


Docker Explorer View


The first view is a tree view of the various connections to Docker daemons. A connection to a Docker daemon is needed before any management of Docker Images or Containers can be performed. On initial start-up, there will be no connections and the Docker Explorer View will display a message regarding this. Note that the Docker Images View and Docker Containers View are controlled by the connection selected in the Docker Explorer View. They will also note there are no connections established yet.


Clicking on the message will bring up the New Connection Wizard.


The wizard allows the user to select a name for the connection and specify its location. For Linux users that have a local daemon running, this will be defaulted to the Unix socket: unix:///var/run/docker.sock. If a custom connection is desired, clicking the "Use custom connection settings" checkbox will allow the user to fill in either a unix socket address or a TCP address. On Mac or Windows systems, a TCP address will be required. Authentication may be required in which case the user should click on the "Enable authentication" check-box and fill in a path to the authentication files to use.

Once the data is filled, the user can test the connection by clicking on the "Test Connection" button or simply hit the "Finish" button.

More than one connection can be specified. To add more connections, click on the LinuxToolsNewConnectionIcon.png icon to bring up the wizard again. To delete a connection, click on the LinuxToolsRemoveConnectionIcon.png icon. To refresh the tree view, click on the LinuxToolsRefreshConnectionIcon.png icon. Refreshing may be required if the user has performed management outside of Eclipse using the docker command.

The Explorer View shows a tree view with the main nodes being the connections. Each connection opens up to reveal Images and Containers nodes which have children nodes for Images and Containers that the connection knows about. Filtering is provided. Simply click on the generic Menu options (down arrow) and click on "Customize View...". This will bring up the following dialog:


From here one can filter out:

  • Dangling Images (intermediate images that are no longer referred to)
  • Intermediate Images (images with no repo tags that are parents of named images)
  • Stopped Containers (this does not include paused Containers)
  • Top-level Images (only show the first repo tag for an Image with multiple tags)

Docker Explorer Context Menu

For both Containers and Images in the Docker Explorer View, right-clicking on a selection brings up the context menu with tasks to perform on the selected item(s). Actions applying to multiple items are only enabled if the action can be performed on all selected items.


For Containers, one can:

  • Start - start a stopped Container
  • Pause - pause a running Container
  • Unpause - continue a paused Container
  • Stop - stop running Containers
  • Kill - kill running Containers
  • Remove - delete stopped Containers
  • Commit - commit the Container to an Image
  • Display Log - display the log for the Container
  • Remove Log - removes the log for the Container from Eclipse Console View


For Images, one can:

  • Run - build a Container and run it
  • Remove - delete selected Images
  • Push - push an Image to a registry
  • Add Tag - add a tag to an Image
  • Remove Tag - remove a tag from an Image with multiple tags

Docker Images View


The Docker Images View is used to manage Docker Images. By default, the View shows only top-level Images that have at least one repo:tag name. The menu options allows you to see all Images by clicking the "Show all images" check-box.


The connection used for the Docker Images View is determined by the latest selection in the Docker Explorer View. Whatever was last selected in the Docker Explorer View is queried for its connection and this is used for the Docker Images View. If there is only one connection, it is defaulted.

There are a number of toolbar actions supported in the Docker Images View:

There are also context menu actions supported:

  • Add Tag - same as the toolbar tag image action
  • Remove Tag - remove a tag from an Image with multiple repo tags

The text entry below the Connection name is used to search/filter the contents of the list. Anything typed in the filter text widget is used to match items in the list (any column) and any row without a match is excluded.

Pull Image

Pulling a Docker Image consists of requesting a repo tag or repository specification. Specifying a repository but no tag will pull all Images from that repo (for example: fedora).

The pull Wizard is used to specify the repository or repo:tag specification.


The user can either fill in the complete name of the image to download or a search can be performed using the Search button. This brings up the Search Image Wizard.


Hitting the Search button will cause a search to list all repositories with the given search term. Hitting Next... shows the various tags that can be selected.


A search is performed only on the official Docker registry. If a user needs to download an image from a private registry, then the full specification of the image, including registry, needs to be made manually in the initial Wizard text box.

Once complete, the user hits the "Finish" button or hits "Cancel" to abort.

The pull of an Image may take a long time. This is because an Image may use several intermediate Images each of which may be several bytes. The Linux Tools Docker Tooling provides status jobs to monitor the download of the various Images and has an overall job created to monitor the status of the pull itself. When complete, refreshing of the Docker Explorer View and Docker Images View is automatic.

Push Image

Pushing a Docker Image consists of specifying an existing repo tag to push. By default, Images will be pushed to the default Docker registry, but if a tag contains a registry specifier in addition to repo:tag, it will be pushed to the specified registry. To specify an external or local registry, use the Tag Image function to add a new tag to an existing Image which has the registry specifier and then push that tag.

The push Wizard is used to specify the tag to push.


Like a pull of an Image, pushing an Image may take a long time. The Linux Tools Docker Tooling provides status jobs for the various Images being pushed (may include needed intermediate Images) and an overall job is created to monitor the status of the push job.

Run Image

The Run Image Wizard is used to create a Container based on an Image.

The first page of the Wizard allows a number of common settings:


  • Image - this field is filled in based on the user's selection
    • Other images are available from the pull-down or the user can type in an Image not currently loaded and click on the Pull Image link.
  • Name - this field must be filled in as this is the name of the new Image
  • EntryPoint - this allows configuring the Container to run as an executable
    • The entry point is an executable to run plus arguments. On the command-line, additional arguments can be specified.
  • Command - this is the command to run in the Container when it starts
    • This field may be left blank if the Image has a default command to run.
  • Ports - the user can choose to expose ports from the Container (self-explanatory)
  • Links - the user can choose to link to other Containers
  • Keep Stdin Open - used to allow input from the Console
  • Allocate pseudo-tty - used to allocate a TTY for the Container (needed if running a shell)
  • Automatically remove the Container on exit - this is used to remove the Container when finished

The second page of the Wizard also has a number of needed settings:


  • Data Volumes - the user can mount Host volumes in the Container or mount other Container volumes
    • This is useful for copying data from the Host into the Container (e.g. an executable).
  • Environment Variables - way of specifying Env variables to use in the Container
  • Enable Resource Limits - this is used to restrict memory or CPU priority for the Container

As of Docker Tools 1.2.0, the Run Image settings are stored in a Run Launch Configuration. You can optionally use the Run Configurations Dialog (Run -> Run Configurations...) to edit or create a Run Image configuration. The same data that appears in the Run Image Wizard is broken up into launch configuration tabs:


  • Main - this tab contains the connection, Image name, Container name, entrypoint, command, and flags such as remove on exit, attach input, and use TTY
  • Volumes - this tab allows a user to mount Host volumes in the Container or mount other Container volumes
  • Ports - this tab allows a user to expose ports from the Container
  • Links - this tab allows links to other Containers
  • Environment - this tab allows specification of environment variables for the Container
  • Resources - this tab allows the user to restrict memory or CPU priority for the Container

Build Image

Building an Image takes an existing Image and modifies it to create a new Image. Typically this involves installing new packages. The specification of the new Docker Image is done via a special file which is always named: "Dockerfile". Clicking on the Build Image icon starts the Build Image Wizard:


There are two fields that need to be filled in:

  • Name - this is the name that will be given to the new Image
    • Note that this name must follow correct repo:tag format.
  • Directory - this is the directory that contains or will contain the Dockerfile

The directory can be specified using the "Browse" button. Once a valid existing directory is specified, the "Edit" button will be enabled, allowing creation and modification of the Dockerfile using a basic editor dialog.

When the Dockerfile is considered complete, hitting the "Finish" button will start the Image build action. When the build is complete, the Docker Images View will be refreshed automatically.

Dockerfile Editor


The Dockerfile editor is a rudimentary text editor with clipboard support (copy, cut, and paste). The Dockerfile is used to specify how to build the new Docker Image. The file contains a set of commands used to build the Image:

  • FROM xxxxxx - this must be the first line and specifies the Image xxxxxx to base off of (e.g. FROM fedora:20)
    • The first line of the file must be: FROM: xxxxxx where xxxxxx is the Docker Image name/id to base the Image off of (e.g. FROM: fedora:20).
  • MAINTAINER name - this sets the Author field of the Image and is optional
  • RUN <cmd | ["executable", "arg0", "arg1" ...]> - this is a command that is run to modify the base Image in either the cmd format or the executable format
    • The cmd form is run in a shell (/bin/sh -c cmd).
    • Typically, this is how you install new packages (e.g. RUN yum install -y gdb). It can also be used to modify the configuration (e.g. sed operations on a config file).
    • These commands are run in the build stage prior to any Container being run and there can be multiple RUN commands specified.
  • CMD - this is the default command that the new Image will run if one isn't specified on Container create.
    • There are three forms:
    • The CMD is not run in build, but only when the Container is created and started.
  • ENV - this specifies one of more environment variables
    • There are two forms:
      • <NAME> <VALUE>
      • <NAME>=<VALUE> <NAME2>=<VALUE2> ...
    • The second format allows multiple environment variables at once. There can be multiple ENV specifiers.
    • Once specified, the environment variable may be referred to later on using the $NAME syntax (e.g. HOME=/home/$USER)
  • LABEL - adds metadata to the Image
  • ONBUILD - use this to specify commands to add to any Image building from this one
    • This is useful for configuration stuff that needs to be done repeatedly in each child Image.
  • ADD - add a file from the host into the Container file system
    • There are two forms:
      • ADD <src>... <dest>
      • ADD ["<src>"... "<dest>]
    • The second form is used to quote names that have white-space.
  • COPY - copy a file from host into the Container file system
    • There are two forms:
      • COPY <src>... <dest>
      • COPY ["<src>"... "<dest>]
    • The second form is used to quote names that have white-space.

For more details, see the official Dockerfile reference

Add Tag

The Tag Image dialog can be brought up directly from the Docker Images View toolbar or using the context menu by right-clicking on an Image.


The dialog is simple and asks for a new tag to add to the Image. The tag should be of one of two forms:

  • <repository>:<tag> where <repository> may be <username/reponame> or <reponame>
  • <registry>:<repository>:<tag> where <registry> contains a "." or ends with a port specifier (":port")

Adding a tag with a registry is the way to push existing Images to local or external registries. By default, Docker pushes Images to its default registry. When pushing to the default registry, a username needs to be specified in the repository specifier because write privileges are prohibited for the base Images (e.g. fedora:20 is the official Docker Image for F20 whereas a user may have a user/fedora:20 copy they have modified).

Remove Tag


The Remove Tag dialog allows the user to remove a tag from an existing Image. This may be done to rename a tag or to keep the number of tags manageable. The Remove Tag menu item is only enabled after selecting an existing Image in the Docker Images View that has multiple tags. The dialog presents the list of possible tags to remove in a drop-down list.

Docker Containers View


The Docker Containers View is used to manage Docker Containers. By default only running Containers are shown. To see all Containers, click on the menu options and click the "Show all containers" check-box.


The connection used for the Docker Containers View is determined by the latest selection in the Docker Explorer View. Whatever was last selected in the Docker Explorer View is queried for its connection and this is used for the Docker Containers View. If there is only one connection, it is defaulted.

The text entry below the Connection name is used to search/filter the contents of the list. Anything typed in the filter text widget is used to match items in the list (any column) and any row without a match is excluded.

There are a number of toolbar actions supported in the Docker Containers View:

  • LinuxToolsDockerContainerStartIcon.png - start a stopped Container
  • LinuxToolsDockerContainerPauseIcon.png - pause a running Container
  • LinuxToolsDockerContainerUnpauseIcon.png - continue running a paused Container
  • LinuxToolsDockerContainerStopIcon.png - stop a running Container
  • LinuxToolsDockerContainerKillIcon.png - kill a running Container
  • LinuxToolsDockerContainerDeleteIcon.png - delete a stopped Container
  • LinuxToolsDockerContainerRefreshIcon.png - refresh Containers list

It should be noted that the various actions above are enabled/disabled based on the state of the current selected Container(s) in the View. Multiple Containers can be selected for an action so long as all Containers meet the enablement requirements.

  • a Container can only be started if it is stopped with a known status
  • a Container can only be stopped, paused, or killed, if it is known to be running
  • a Container can only be unpaused if the Container is known to be paused
  • a Container with unknown/missing status can only be deleted

The following context menu actions are supported:

Commit Container

The Commit Container dialog is simple.


The user is required to enter:

  • Name - name of the new Image being created
    • The name must be a valid repo tag name.
  • Author - optional name to add as the Author of the Image
  • Comment - optional comment to add for the Image

Display Log

The Display Log action displays the stdout/stderr output for a Container in either the Console View or the Terminal View, depending on whether the Container specified use of a TTY.

For Containers that run with the TTY flag enabled, the output goes to the Terminal View:


For Containers that run without a TTY, the output is shown in the Console View:


In the example above, each entry in the log is preceded by a time-stamp. This can be controlled using Window->Preferences->Docker->Logging.


From there, one can control:

  • logging on start - by default starting a Container will output stdout/stderr to a console in the Console View
    • Each log is in a separate console that can be removed using the Remove Log context menu-item for the Container
  • timestamps - by default they are added

Properties View

The Properties View will respond to selections in the three Docker Tooling Views: Docker Explorer View, Docker Images View, and the Docker Containers View. The data shown will depend on what is being selected:

  • Docker Connection
  • Docker Image
  • Docker Container


For a Docker Image and Docker Container, there are two forms of data:

  • Info - what is shown from the docker command when listing Images or Containers
  • Inspect - what is shown from the docker command when inspecting an Image or Container (additional data)


Copyright © Eclipse Foundation, Inc. All Rights Reserved.