Container Images

Container Images

The Pipekit installation consists of several container images, each of which is responsible for a different part of the Pipekit service. This page documents the images and their respective repository:

Image Repository	Image Name	Public or Private?	Required?	Reason image is optional
pipekit13	cli	Public	No	Used for accessing the Pipekit CLI in a container
pipekit13	pipekit-agent	Public	Yes
pipekitprivate	events-handler	Private	No	Only required if you integrate Pipekit with a git provider.
pipekitprivate	id	Private	Yes
pipekitprivate	messenger	Private	Yes
pipekitprivate	pipekit-init	Private	Yes
pipekitprivate	ui	Private	Yes
pipekitprivate	users	Private	Yes

In addition to the images listed above, the Pipekit installation also requires the following third-party image:

Image Repository	Image Name	Public or Private?	Required?
fluent	fluent-bit	Public	Yes

There may be additional images required for the installation, depending on how you choose to configure your third party dependencies.

Private Images

You will require a Docker Hub account with access to the pipekitprivate repository to pull the private images. This will be provided to you as part of your Pipekit subscription. Please contact us at [email protected] for more information.

You will be permitted to attach a single Docker Hub account to the pipekitprivate repository. We recommend that you use this account to pull the images onto your own managed repository.

Non Root Users

All of the Pipekit container images use a non-root user by default.