GLU supports pushing an instance of a GLU.Engine as a Docker container to a container registry such as Dockerhub, Azure Container Registry or AWS Elastic Container Registry/ ECR.
Whichever container registry you choose to use, the configuration and support are your responsibility.
If using AWS ECR the configuration in the GLU.Console is unique, please refer to the guidelines here AWS ECR.
For some container registry systems like Azure when the Docker image repository doesn’t exist, it will be auto-created when GLU pushes to the container registry.
When in the Build Manager, working in the GLU.Engine Settings tool, on the Docker Tab, if the ‘Skip Docker’ checkbox is not ticked, a Docker container will be produced and sent to the specified container registry. Additionally a downloadable .JAR file will be created and be available for local download.
All fields on the Docker tab as below are mandatory.
| name | Value | Description |
|---|---|---|
| docker.url | docker.io | path to the docker.io instance |
| docker.username | glu global | username to the docker instance |
| docker.skip | false | true or false, When set to false docker will be used. |
| docker.password | myDockerPassword | password to the docker instance |
| docker.image.repository | gluglobal | in docker the repository name |
See GLU.Engine Settings for further details on how to use the dialogue box.
It should be noted that working with dockerhub can be confusing … for example …
When you create a new account, the initial repository will be the same name as the account which was created. In this example below, switchtesting is the name of the Repository, even though the account was created with an account name switchtesting.
As can be seen from the docker settings below, the Docker username and the Docker Image Repository are the same. In this case this is what is needed to push to the repository.
