Docker images for NIOT-E-TIJCX-GB-xx devices can be built automated on the web, how does that work?
Docker images for NIOT-E-TIJCX-GB-xx devices can be built automated on the web, how does that work?
Preconditions for an automated build are:
You need a Docker Hub account
You need a Github account
You need to create a repository on Docker Hub
How to setup a Docker image repository to be built automated on Docker Hub servers can be read here.
Next to a Docker Hub online account a Github account is needed to allow Docker Hub accessing your sources during the web build process.
A file named Dockerfile is basis for any automated built process whether it is built remotely on the web or locally using the Docker (CLI) Command Line Interface (if you have access to it).
This file contains the command instructions in adjacent order executed during the build process. There is just a set of maybe 10 keywords the Dockerfile interpreter understands.
During creation of a new repository on your Docker Hub registry you can specify whether or not it is of type automated.
If so you have to link it to the Github sources. After that you can immediately start the build process once the Github account contains the Dockerfile at least. When finished the built image will be placed on your repository ready for download.
There is a Docker Hub example we build in an automated way. It enables the gateway's DVI port and outputs a Desktop environment to it. Any repository configured to automated builds offers a link to the Github sources on its landing page:
On Github you find the sources of the repository including the Dockerfile:
For the example above the Dockerfile looks like this:
