Use Single Container

JFrog Connect enables you to quickly deploy a single container from any private repository directly to your edge devices.
Create an update flow that uses the Deploy Containers action block. When you select the Single Container option, you will be able to pull a container image directly from a repository, whether it is public or your own private repository.


Completed the procedures in Deploy Containers.

Configure Single Container Options

Enter the following information:
  • Image URI: The unique path where the container image is located and the image file name. For example: platform-URL/base-repo/docker-repo/docker-image
  • Image Tag: The tag of the image.

Add Run Flags

  1. 1.
    Click Add Run Flags to enter the run flag information.
  2. 2.
    Choose a command from the list and then enter the run flag. These are the same flags used in the docker run command.
  3. 3.
    Click Add More if you want to enter an additional run flag. You can run as many as you want.

Add Docker Run Command

The Docker run command structure uses official docker commands, but in a structured manner.
docker run [OPTIONS] IMAGE [COMMAND] [ARG...]
To add the command to run in the container, remove all parts except for [COMMAND] [ARG…]
For example, in the following CLI deployment:
docker run alpine:latest echo hello world
the command will be: echo hello world
For [OPTIONS] use the Docker Run flags as shown below.

Docker Run Flags

Choose the Run Flag from the dropdown list.

Delete Previous Used Image

Mark the checkbox to delete the current image after the new container has been deployed. (This is the default setting.)

Configure On Failure Options

Configure your On Failure policy and instructions for rolling back, if necessary.
On Failure enables you to define what happens upon failure of the Deploy Containers action block. By default, the first container is stopped, and if the block fails, the new image is deleted and the previous container will start running once again. This returns everything to the previous state.
Failures that are caused by container logic (e.g., Command fails or Invalid image architecture) are handled by the Docker Compose binary and are not regarded as a block failure.

Complete the Configuration

Save your action block configuration.
If you are adding more action blocks to the workflow, continue to the next one. Otherwise, complete your workflow configuration and save it.

What’s Next?

Learn how to go on to the next step and run the update deployment.