sentry-launchpad-fips

packaged by Chainguard

Chainguard Container for sentry-launchpad-fips

FIPS-enabled Sentry service that analyzes iOS and Android app bundles for size insights

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/sentry-launchpad-fips: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 sentry-launchpad-fips image is comparable to the upstream launchpad image that self-hosted Sentry runs (ghcr.io/getsentry/launchpad), with the following differences:

• It runs launchpad worker by default as the app user (UID 1000) from /app, like upstream. The Python environment lives in /usr/share/sentry-launchpad/venv, which is first on PATH, and the launchpad command is at /usr/bin/launchpad.
• Upstream's image also installs bundletool, apksigner (with a Java runtime), cwl-demangle, libdispatch, and prebuilt Apple strip and ld binaries. These tools are not available as Chainguard packages, so Android App Bundle (AAB) analysis, APK signature inspection (launchpad distribution), Swift symbol demangling, and Apple binary stripping are unavailable. APK size analysis and the background worker work as upstream, and the image includes the zip, unzip, and file tools that upstream also installs.
• Like other Chainguard Containers, it has a minimal design with no package manager, and it has few to zero CVEs.

FIPS Support

The sentry-launchpad-fips image ships Chainguard's validated redistribution of the OpenSSL FIPS provider module. Python's hashlib and ssl modules, cryptography, grpcio, and confluent-kafka all use the system OpenSSL in FIPS mode instead of the copies that the PyPI wheels bundle. See the FIPS-enabled images guide for supported configurations and operating requirements.

The MD5 and SHA-1 digests that launchpad computes for duplicate file detection are marked as non-security uses so they keep working in FIPS mode. The bundled lief library, which launchpad uses to parse Mach-O and ELF binaries, statically includes mbedTLS; launchpad only uses lief for parsing, not for cryptography.

Getting Started

Analyze an Android APK and print the size report as JSON. This example mounts the current directory, which contains app.apk:

docker run --rm -v "$PWD:/work" cgr.dev/ORGANIZATION/sentry-launchpad-fips:latest \
  size /work/app.apk --quiet | jq '{app_id: .app_info.app_id, download_size, install_size}'

{
  "app_id": "dev.chainguard.sizetest",
  "download_size": 905,
  "install_size": 62064
}

Configuration

In self-hosted Sentry, launchpad runs as a background worker that pulls tasks from taskbroker and reports results to Sentry. Run it on the same Docker network as those services, with the settings self-hosted's launchpad-taskworker service uses. LAUNCHPAD_RPC_SHARED_SECRET must match the secret Sentry is configured with:

docker run -d --name launchpad --network <sentry-network> \
  -e LAUNCHPAD_WORKER_RPC_HOST=taskbroker:50051 \
  -e LAUNCHPAD_WORKER_CONCURRENCY=1 \
  -e SENTRY_BASE_URL=http://web:9000 \
  -e LAUNCHPAD_RPC_SHARED_SECRET=<shared-secret> \
  cgr.dev/ORGANIZATION/sentry-launchpad-fips:latest worker

To use this image in self-hosted Sentry, set LAUNCHPAD_IMAGE in your .env file to cgr.dev/ORGANIZATION/sentry-launchpad-fips:latest. SENTRY_OPTIONS_DIR defaults to /etc/sentry-options, where the image ships launchpad's options schema.

Documentation and Resources

• launchpad on GitHub
• Self-hosted Sentry documentation
• Size Analysis in Sentry

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.