traccar

packaged by Chainguard

Chainguard Container for traccar

Minimal image for Traccar, the open-source GPS tracking system server.

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/traccar:latest

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

Compatibility Notes

Chainguard's traccar image is comparable to the upstream traccar/traccar image, with the following differences:

• Like all other Chainguard Containers, traccar features a stripped-down, minimal design with few-to-zero CVEs.
• The image runs as a non-root user (65532) by default, rather than root.
• Traccar is installed at /usr/share/java/traccar; the upstream /opt/traccar path is provided as a compatibility symlink, so the same configuration, mount, and entrypoint paths continue to work.

Getting Started

The image starts the tracker server directly, using the shipped example configuration at /opt/traccar/conf/traccar.xml.

Run the server, exposing the default web UI on port 8082:

docker run --rm -p 8082:8082 cgr.dev/ORGANIZATION/traccar:latest

Then open http://localhost:8082 in a browser and register a user through the built-in UI.

Providing a custom configuration

For real deployments, mount your own traccar.xml (see the configuration reference) and override the command to point at it:

docker run --rm -p 8082:8082 \
  -v "$(pwd)/traccar.xml:/opt/traccar/conf/traccar.xml:ro" \
  cgr.dev/ORGANIZATION/traccar:latest

The Traccar install directory (/opt/traccar) is owned by the runtime user (65532), so the default configuration boots without additional setup: the tracker-server.log, the embedded H2 database, the override directory, and any media uploads are created under /opt/traccar by the non-root user — the same relative paths the upstream image writes as root.

For real deployments, point Traccar at persistent storage from your traccar.xml (database files, media uploads, logs) and mount those volumes at paths owned by UID 65532.

Deploying with Helm

Traccar publishes an official Helm chart (traccar/traccar-helm). Point the chart at this image and align the pod's security context with the image's non-root UID (65532) — the chart defaults to runAsUser: 1000, which does not match this image:

helm repo add traccar https://traccar.github.io/traccar-helm/
helm install traccar traccar/traccar \
  --set image.repository=cgr.dev/ORGANIZATION/traccar \
  --set image.tag=latest \
  --set podSecurityContext.fsGroup=65532 \
  --set securityContext.runAsNonRoot=true \
  --set securityContext.runAsUser=65532

By default the chart provisions a MySQL database. To use a different database (or the bundled H2 store) provide your own configuration through the chart's configOverride value — see the chart values and the Traccar configuration reference.

Documentation and Resources

• Traccar Documentation
• Traccar API Reference
• Traccar Configuration File
• Upstream repository

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.