Docker
Supported Commands
Use these commands with the RepoFlow server:
docker pull
docker push
docker login (Using username and password)
Note: Commands that run locally are not listed here but will work as expected.
BuildKit Provenance Attestations
RepoFlow supports Docker BuildKit provenance attestations pushed with
docker buildx build --provenance=mode=max --push.
In this flow, BuildKit pushes the image as an OCI index. The index references
the runtime image manifest and a separate attestation manifest, which contains
the application/vnd.in-toto+json SLSA provenance payload.
RepoFlow does not support directly tagging an in-toto attestation manifest as the image manifest itself. That is not the standard Docker BuildKit provenance push flow, but it may appear with custom OCI clients or manual registry API uploads.
Package Labels
RepoFlow now extracts and displays certain labels on the package page, including:
org.opencontainers.image.descriptionorg.opencontainers.image.licensesorg.opencontainers.image.source
This makes it easier to access important package metadata directly from the package page.
Remote repositories examples
Docker hub
To configure Docker Hub as a remote repository, use the following URL:
https://registry-1.docker.io
GitLab
For example, to download the image:
registry.gitlab.com/gitlab-org/gitlab-runner/ci-kubernetes-integration-tests:v1
You need to set the remote repository URL to:
https://registry.gitlab.com/gitlab-org
Then, to pull the image from the configured remote repository, use:
docker pull api.repoflow.io/<workspace>/<remote-repository>/gitlab-runner/ci-kubernetes-integration-tests:v1
Catalog API
Lists all images stored in a local Docker repository.
Request
GET https://api.repoflow.io/v2/<workspace-name>/<repository-name>/_catalog?limit=<number>&offset=<number>
Response
{ "repositories": ["library/alpine", "myapp/service"] }
Notes
- Default limit: 1000, max 2000
- Supports pagination with
offset - Requires read access