2763-2401/211-1000

Using Docker® Images on ctrlX OS Note! Until further notice, this software is only available in beta status. Contact our support team to find out more! Container technology is very popular in computer science and software development. In this context, containers are standard software units that combine the program code and all its dependencies so that the desired application can be executed quickly and reliably in another computer environment, even under different operating systems (Linux, Windows, MacOS). Since its debut in 2013, Docker Inc. has accelerated the development and spread of this technology using its popular open-source container runtime environment called Docker Engine. Running containers on the Docker Engine requires an image that contains everything required to run an application: the program code, the runtime environment, tools, libraries, and settings. This means they can be easily transported and installed as files. [Docker Hub](https://hub.docker.com/) is the world’s largest repository for such container images. [Docker Inc.](http://docker.com/) also offers Docker Desktop, which developers can use to create, run, and share their containerized local development applications. [Docker Desktop](https://www.docker.com/products/docker-desktop/) can be used to create images of software applications, run and manage containers and much more. The Container Engine App makes it possible to isolate Docker images on the ctrX OS-based controller as containers and run them autonomously. It represents the interface between the resources of the controller and the running containers. A Docker image application for the controller can be created from a Docker image and the corresponding Docker configuration files using a snap template. These apps are visible in the App Manager as well as native ctrlX OS apps. Please note the following warranty restrictions and IT security considerations: The ctrlX OS Container Engine App itself fully complies with WAGO quality standards and ctrlX OS security mechanisms. However, since Docker technology has several inherent security aspects, WAGO cannot take responsibility for Docker images (so-called custom Docker images) not provided by WAGO that are executed on the Container Engine. Users who provide their own Docker images and use them on the ctrlX OS must note and confirm the following: WAGO does not guarantee custom docker images that run on a ctrlX OS-based controller. The provider of a custom Docker image on a ctrlX OS-based controller must ensure that this image does not violate the built-in ctrlX OS security mechanisms. The [ctrlX AUTOMATION App Developer Guideline](https://boschrexroth.github.io/ctrlx-automation-sdk/appdevguide.html) and the associated guidelines in the SDK provide information on how to fully support these mechanisms. If the Docker custom image does not meet the guidelines, accessing the ctrlX OS system resources by the image can lead to security and availability problems in the controller. Vendor must monitor and harden the image accordingly to avoid any impact on the ctrlX OS system. Please refer to the respective safety recommendations of [Docker Inc.](http://docker.com/) for more information. This app was developed based on the source code published by Docker Inc. It is not supported or published by Docker Inc. Docker and the Docker logo are trademarks or registered trademarks of Docker, Inc. in the United States and/or other countries. Docker, Inc. and other parties may also have trademark rights to other terms used herein. ctrlX, ctrlX Automation and ctrlX OS are registered trademarks of Bosch Rexroth AG.