Chainguard Container for arangodb

ArangoDB is a native multi-model database with flexible data models for documents, graphs, and key-values. Build high performance applications using a convenient SQL-like query language or JavaScript extensions.

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/arangodb:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

The Chainguard arangodb image is comparable to the official arangodb image. Note that the Chainguard arangodb image does NOT run as root, but rather as the arangodb user.

ArangoDB Pods are using readonly root filesystem, so the containers cannot write the logs to the default location /var/log/arangodb3. Instead, the logs should be written to the stderr for best practice. ArangoDB uses /data as the default data directory, which is mounted as a persistent volume. You may need to pass the following flags to the ArangoDeployment manifest:

• --log.file=-
• --temp.path=/data/tmp
• --javascript.app-path=/data/apps

Getting Started

Docker Usage

To run ArangoDB using Docker:

docker run -d --rm --name arangodb -e ARANGO_ROOT_PASSWORD=password -p 8529:8529 cgr.dev/ORGANIZATION/arangodb:latest

Wait for the container to be ready:

# Check if ArangoDB is available
curl -fsSL http://localhost:8529/_admin/server/availability -u root:password

Test basic functionality:

# Check version
curl -fsSL http://localhost:8529/_api/version -u root:password

# List databases
curl -fsSL http://localhost:8529/_api/database -u root:password

# View statistics
curl -fsSL http://localhost:8529/_admin/statistics -u root:password

Kubernetes Deployment

You can use Helm to deploy the arangodb container image using the ArangoDB Kubernetes Operator and start a minimal ArangoDB cluster.

Start by installing the operator:

helm repo add arangodb https://arangodb.github.io/kube-arangodb
helm repo update

helm install arangodb arangodb/kube-arangodb \
  --version my-version

Then deploy a cluster with Chainguard's arangodb container image:

curl -O https://raw.githubusercontent.com/arangodb/kube-arangodb/master/examples/simple-cluster.yaml

Then apply it:

kubectl apply -f simple-cluster.yaml

Replace the default image with the Chainguard version

kubectl patch arangodeployment example-simple-cluster --type='merge' -p '{"spec": {"image": "cgr.dev/ORGANIZATION/arangodb:latest"}}'

To test that the container is working correctly, create a collection:

curl -k -u root: -X POST --header "Content-Type: application/json" \
  --data '{"name":"testcol"}' \
  https://127.0.0.1:8529/_api/collection

Then use curl to view the collection:

curl -k -u root: https://127.0.0.1:8529/_api/collection

Documentation and Resources

• Using the ArangoDB Kubernetes Operator
• kube-arangodb GitHub Repository
• Helm Chart Documentation
• API Reference for ArangoDeployment V1

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.