IBH Link UA:Docker
Overview
Supported IBH Link UA quad-core devices can run Docker containers directly on the gateway. This allows edge applications, protocol converters and supporting services to operate close to the machine network.
Requirements
- An IBH Link UA model with Docker support.
- A suitable SD card inserted in the device.
- Sufficient free storage and memory for the intended containers.
- Network access to the required image registry.
- A current configuration backup before major changes.
Enable Docker
Open the Docker page in the web interface and enable the Docker service. Apply the settings and verify that the service status changes to running. The service can also be configured to start automatically with the device.
Images
Docker images can be pulled from a public or private registry. The image overview shows the available local images. Images that are no longer used can be removed to free storage space.
For a private registry, enter the registry address and the assigned credentials on the registry login page before pulling an image.
Containers
The container overview provides the available management functions:
- create a container from an image
- start, stop and restart a container
- inspect the current container status
- display or download the container log
- save or export a container
- delete containers that are no longer required
Ports, volumes, environment variables and restart behavior must be configured for the application. Host paths should remain within the directories allowed by the IBH Link UA.
Docker Compose
Complete applications can be managed through a Compose YAML file:
- Create or adapt the Compose file for the target device.
- Upload the YAML file on the Docker page.
- Run the syntax and configuration check.
- Correct reported errors before applying the project.
- Apply the Compose configuration and check the status of all services.
Compose files can be downloaded again for backup and deleted when they are no longer needed. Required host directories within the permitted path area can be created automatically when the configuration is applied.
Portainer
Portainer can optionally be used for extended container administration. Access to Portainer should be limited to the management network and protected with a strong password.
Troubleshooting
- Docker does not start: Check the device model, SD card, available storage and Docker activation.
- Image cannot be pulled: Check DNS, gateway, registry address and credentials.
- Container stops immediately: Inspect the container log, command, environment variables and mounted paths.
- Port cannot be reached: Check port mapping, firewall rules and whether the service inside the container is listening.
- Compose configuration is rejected: Validate YAML indentation, image names, volumes and allowed host paths.
- Storage is full: Remove unused containers and images after creating any required backups.