This package provides both a library and a CLI utility to manage Compose Apps built by FoundriesFactory®. For more detailed information about FoundriesFactory® Compose App, please refer to the user documentation. Essentially, a FoundriesFactory® Compose App adheres to the Compose specification. FoundriesFactory® offers mechanisms for building, packaging, and distributing Compose Apps in the form of OCI images. This utility enables users to pull Compose Apps from the FoundriesFactory® App Hub and manage them on a device or a local host. This includes tasks such as installation, running, stopping, etc.
git clone https://github.com/foundriesio/composeapp.git
cd composeapp && make
As a result, the composectl binary should appear in the ./bin directory.
Compose Apps' data are spread across three locations on a local file system:
- The App store directory - all app blobs are stored in this location, by default it is
~/.composeapps/store. - The App project or compose directory - where the docker compose YAML along with its complementary files are stored, by default in
~/.composeapps/projects. - The docker engine store - a few sub-directories in the docker engine data root, by default in
/var/lib/docker.
The App store and project directories can be specified via the --store/-s and --compose/-i parameters respectively.
The docker engine store is determined by the docker daemon instance that the utility communicates to via a socket.
By default, the utility talks to the docker daemon through unix:///var/run/docker.sock,
which in turn stores image layers and containers data under /var/lib/docker.
The docker daemon socket can be specified in the --host/-H parameter.
Also, the composectl utility respects DOCKER_HOST environment variable, which is another way to specify the docker daemon socket.
Prior to communicating with the FoundriesFactory® App Hub authentication should be set.
It can be done either by logging at the hub docker login hub.foundries.io -u "doesnotmatter" -p <FoundriesFactory token>
or setting the docker credential helper by running fioctl configure-docker command.
The FoundriesFactory token can be obtained at https://app.foundries.io/settings/tokens/.
The both methods updates a docker configuration file on a local host (e.g. ~/.docker/config.json).
Make sure to backup it before running the aforementioned commands.
Once the authentication is set, Compose App can be pulled for the hub. At first, the App's URI should be found.
To do so, a user can run fioctl targets list and fioctl targets show compose-app <version> <app name>.
The last command outputs the target's app URI.
composectl pull <app URI> [<app URI>]
The pull command fetches all apps specified in the parameter list. The apps' blobs are stored in the App store. The utility checks integrity of the pulled App, it implies checking integrity of each App's blobs/elements during the pull process.
Once app is present in the local app store, a user can perform the following actions over it.
Effectively, the command checks integrity (sha-256 hash) of each app blob, i.e. an overall app's Merkle tree, starting from the top level element - the app manifest.
composectl check <app URI> [<app URI>]
composectl install <app URI>
composectl uninstall <app URI | app name>
composectl run <app name> [<app name>] | --apps=<comma,separated,app,list>; --apps="" - run all apps
composectl stop <app name> [<app name>] | --all
composectl rm <app name> [<app name>] [--prune]
composectl prune
The dev&test environment based on docker compose contains all required elements to build, manually test, as well as run automated tests. To launch the environment and enter into its shell just run:
./dev-shell.sh
It will take some time to start the environment for the first time because:
- The docker daemon (dind) and the registry container (distribution) images have to be pulled.
- The dev&test container should be built.
Once you are logged into the container shell you can build and run the composectl utility, test it manually
and run automated tests:
./dev-shell.sh
make test-e2e