Registries

A registry on this platform is a GitLab project that contains no source code. It stores packages or container images, and its wiki contains the instructions for using it: the index URL, how to authenticate, and the commands to pull and publish.

The repository is disabled in these projects, so opening one takes you straight to its wiki. Browse the contents under Deploy → Package registry, or Deploy → Container registry for images.

Follow the wiki

A registry's wiki is maintained together with the registry itself. If the wiki and this page differ, follow the wiki.

Where to find your registries

Your registries are in the registries subgroup of your top-level group, with one project per type:

<your-organization>/
└── registries/
    ├── apt/        ← Debian and Ubuntu packages
    ├── choco/      ← NuGet and Chocolatey packages
    ├── conan/      ← C and C++ packages
    ├── docker/     ← container images
    ├── generic/    ← files that fit no other type
    ├── maven/      ← Java packages
    └── pip/        ← Python packages

Each type is enabled individually, so your group has those that were requested for it, and what you see under registries/ is what you have. GitLab also supports npm and Terraform registries, and any of them can be requested.

Container images

The container registry is at registry.code.vector.cloud.

From your computer, log in with a personal access token:

docker login registry.code.vector.cloud
# Username: your GitLab username
# Password: a personal access token with the read_registry scope

docker pull registry.code.vector.cloud/<your-organization>/registries/docker/<image>:<tag>

In a job you need no token; every job already has one:

build_image:
  tags: [linux]
  image: docker:latest
  services:
    - docker:dind
  script:
    - docker login -u "$CI_REGISTRY_USER" -p "$CI_JOB_TOKEN" "$CI_REGISTRY"
    - docker build -t "$CI_REGISTRY_IMAGE:$CI_COMMIT_SHA" .
    - docker push "$CI_REGISTRY_IMAGE:$CI_COMMIT_SHA"

Reusing a prebuilt image is usually faster than installing a toolchain in every job, and it means you debug the same environment the pipeline runs in. See Local setup.

Authentication

Where Use
In a job CI_JOB_TOKEN: already there, no setup
On your computer A personal access token with the read_registry / read_package_registry scope

Never commit a token

Tokens belong in your local credential store or in a masked CI/CD variable, never in .gitlab-ci.yml, a Dockerfile, or any file you commit. See Secrets.

Publishing your own packages

You can publish into projects in your own group. GitLab does not enforce a structure, so pick one of these two conventions and stay with it:

  • A registry project per package type, mirroring how Vector-provided packages are organized. Better where several teams consume the same packages.
  • The root group of your project, keeping all packages for one product together.

Full syntax per package type is in the package registry documentation and the container registry documentation.

Getting something added

Ask your Vector contact for a package, a tool, or a registry type your group does not have yet.

Publicly available Vector packages are consumed through veHub. See Tools Under External Repository.