1. Home
  2. GLU.Guide
  3. GLU DevOps
  4. Running GLU.Engines in Docker Containers

Running GLU.Engines in Docker Containers

GLU supports deploying a GLU.Engine instance as a Docker container to various container registries like 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 your are using AWS ECR, the configuration in the GLU.Console is unique, please refer to the guidelines provided in the AWS ECR documentation.

For certain container registry systems like Azure, if the Docker image repository doesn’t exist, it will be automatically created when GLU pushes to the container registry.

In the Build Manager, while 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 available for local download.

All fields on the Docker tab as below are mandatory:

docker.urldocker.iopath to the docker.io instance
docker.usernameglu globalusername to the docker instance
docker.skipfalsetrue or false, When set to false docker will be used.
docker.passwordmyDockerPasswordpassword to the docker instance
docker.image.repositorygluglobalin docker the repository name

See GLU.Engine Settings for further details on how to use the dialogue box.

It’s important to note that working with Dockerhub can be confusing, especially regarding repository names.

For example, when you create a new account, the initial repository will have the same name as the account that was created. So, if your account name is “switchtesting,” the initial repository created will also be named “switchtesting.” This can sometimes lead to confusion, as users might expect the repository name to be different from their account name.

As can be seen from the docker settings below, the Docker username and the Docker Image Repository are the same. This was needed to push the Docker configuration to the repository in this use case below:

Was this article helpful?

Related Articles

Need Support?

Can't find the answer you're looking for?
Contact Support
Fill the form and we’ll contact you shortly

    I agree with

    We uses cookies to make your experience on this website better. Learn more
    Accept cookies