Creating a new Container

Edit online

Procedure

  1. Load the Container image into Docker running on your server.

    Example: Loading Appliance Containers

    Loading an Appliance Container image stored on a remote HTTP server 

# curl http://example.website/clevos-3.19.3.1-accesser-container.tar.gz | sudo docker load 

Loading an Appliance Container image stored locally 

# cat clevos-3.19.3.1-accesser-container.tar.gz | sudo docker load
  2. List the Container images to find either the repository/tag pair or image ID to start a Container.

    Example: Loading Appliance Containers

    The docker run command uses either the repository/tag pair or image ID to identify the Container image. 

# sudo docker images
REPOSITORY        TAG        IMAGE ID      CREATED         VIRTUAL SIZE
clevos-manager    3.19.3.1   2555e9b7c741  4 days ago      4.37 GB
clevos-accesser   3.19.3.1   c260ab58b9ee  4 days ago      3.51 GB

To load an Appliance Container, the command would use either: 

# sudo docker run ... clevos-accesser:3.19.3.1 

or 

# sudo docker run . . . c260ab58b9ee
  3. Create an empty directory on the Docker host to store persistent data of the Appliance Containers. Since release 3.19.3, appliance Containers are running as non-root user with UID 1000670000 and GID 600 instead of a root user. The ownership of the persistent directory needs to be set accordingly. 
    Creating a persistent directory for the Appliance Container on the Docker host

# mkdir -p /home/data/container-data-1

Change ownership of persistent directory to 1000670000:600

# chown 1000670000:600 /home/data/container-data-1
  4. Start a new container using —env to specify environment variables as documented in Manager Administration. If successful, the Container ID is written to stdout.
    Example: Loading Appliance Containers
    Starting an Appliance Container:

# sudo docker run -itd --env="DS_MANAGER_IP=192.168.79.15"
--env="DS_MANAGER_AUTOACCEPT=true"
-v /home/data/container-data-1:/container-persistence:rw
--net=host clevos-accesser:3.19.3.1  

Returns: 
c644228d71f84be86420b44ed53f9927401fcd5c638e4ce77fdd72ec28b47d431

1 This is the Container ID.
  5. Approve the Container Instance in the Manager Web Interface according to the procedure found in managerAdmin_configuration_approveregistereddevices.html#configuration_approveregistereddevices.
    Note: Once it is running, an Appliance Container can be used like its corresponding Appliance, subject to the other limitations described in this guide.