Docker Compose
JFrog Connect Docker Compose integration enables you to utilize Docker Compose exceptional capabilities to deploy multiple containers to your edge devices.

Overview

Enables you to deploy and manage multiple containers by using Docker Compose capabilities.
Even if another registry is integrated, Docker-Compose utilizes the incorporation of Artifactory in order to deploy to edge devices.
Requires Agent Version 6.0 and above.
Read JFrog Account integration for further information.
Docker Compose Utilizes JFrog Container Registry, you may read more about it in the JCR Docs

Deploying Docker Images

The recommended approach to manage containers on edge devices is using docker-compose.
JFrog Connect utilizes docker-compose and its advantages in order to deploy container images onto your devices.

Prerequisites

  • docker installed on your devices.
  • docker compose or docker-compose installed on your devices.
  • A docker-compose configuration file located inside your JFrog Artifactory

Configuration

Artifactory Path

Select the path in JFrog Artifactory where the docker-compose file is located.

Destination Path on Device

The directory on the device that the docker-compose file will be pulled into.
This is also the project-directory for the docker-compose binary (read more).
The directory on the device must exist beforehand, otherwise, the update will fail.
JFrog Connect does not automatically create directories when deploying updates, you may create a folder using the "Run Command" block in the General Section.

On Fail

Allows you to define the occurrences upon failure of the JFrog Containers block.
By default, when the block fails, the docker-compose file is automatically reverted to the previous state.
Failures that are caused from container logic (e.g., Command fails, Invalid image architecture) are handled by the docker-compose binary and are not regarded as a block failure.
It is recommended to add restart: always to your service configurations in order to make sure docker-compose automatically restarts the service.
In order to allow a Rollback functionality, deployments require your device's free memory to be higher than the update size.
To calculate how much free memory is required, follow the equation below
Free Memory Required > Current directory size + Update size + 10MB
To read more about On Fail configuration, refer to the Rollback section.
Copy link
On this page
Overview
Deploying Docker Images
Prerequisites
Configuration
Artifactory Path
Destination Path on Device
On Fail