Eclipse Docker Tooling for Neon
In this article Roland Grunberg, Software Engineer at Red Hat, presents a handful of new features available in Eclipse Neon. If you find yourself using Docker images/containers, you should try out this plugin as it’s sure to simplify various use cases.
Eclipse Neon (4.6.0) marks the second major release (2.0.0) of the Eclipse Docker Tooling. You can get the tooling from within the Neon update sites themselves that ship with Eclipse, the Eclipse Marketplace, or from the Linux Tools Project’s Eclipse Docker Tooling update site.
While we certainly wanted to provide newer features for users, a lot of our efforts went into fixing many different bugs and usability issues that came up since our initial Mars release, and that hadn’t been addressed in any of the subsequent minor releases (Mars.1, and Mars.2). In total, we fixed 56 reported bugs for the 2.0.0 release (part of the 5.0.0 Linux Tools release). As a result the tooling has become more stable.
However there are a few noteworthy features that have made the simultaneous release with Eclipse Neon.
We wanted to provide some kind of Dockerfile editor as part of our tooling for a while now, so it was great to receive such a contribution from Tobias Verbeke of Open Analytics.
The editor provides users with content assist and hover help for various Dockerfile commands along with some basic syntax highlighting.
Executing shell in a container
Often, containers are started with some process running in the foreground making it impossible to get a shell environment into a container. By using the docker-exec endpoint of the remote API and launching, we’re able to get a shell into pretty much any running container.
This is provided through a Target Management (TM) Terminal which provides a better experience than the standard Eclipse Console.
Improved Connection Support
While users will often create Docker daemon connections that are active, these connection can be taken down, or go offline for various reasons. Such a state should be reflected to the users, with the option to remedy the situation if possible.
We now make the connection icons for disabled connections appear grey in the Docker Explorer View, with no underlying images/containers being shown from any view (Containers, Images, Explorer views). Users can try enabling the selected connection by clicking the enable connection button from the Explorer View’s toolbar.
In additon to this, connections may now be edited in the event that certain information has changed (eg. IP address has changed). This is done by right clicking on a selected connection in the Explorer View and clicking the “Edit…” option.
Pushing, pulling, and searching for authenticated registries
We’ve supported pushing, pulling, and searching against the Docker Hub registry, but never against third party registries, or any kind of account authentication. In Neon we now add support for pulling, pushing, and searching against standard registries (v1, and v2) along with the ability to store authentication credentials for the operations.
As part of the pull, or push operation, users can specify the host (and port) on which the registry may be reached. For a pull, users can then specify the image directly, or query the registry using the Search Wizard.
For push operations, users need not qualify the tag they wish to push with the location of the registry, as this is done automatically.
These are just some of the new features available in Neon. We received a lot of feedback and we hope to use it to improve some of our newer features as well as to decide what we need to be working on next. If you find yourself using Docker images/containers, we would recommend you try out this plugin as it’s sure to simplify various use cases. For more detailed information on features, be sure to have a look at our Eclipse Docker Tooling User Guide.
For more information and articles check out the Eclipse Newsletter.