floci

packaged by Chainguard

Chainguard Container for floci

Local AWS service emulator for development and testing

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

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

Compatibility Notes

This image is comparable to the floci image on Docker Hub. Like upstream, it publishes a standard and a -compat variant to the same repository:

• latest and X.Y.Z: the standard image, with Floci and its entrypoint scripts.
• latest-compat and X.Y.Z-compat: adds the AWS CLI, python3 with boto3 and pip, awslocal, and the init-hook directories. AWS defaults are preset, so aws commands inside the container reach Floci without --endpoint-url. Use it when init hooks run AWS CLI or boto3 code.

User: Both tag variants of the Chainguard image run as the non-root floci user (UID 1001, group 0). Upstream's standard image starts as root and then drops to UID 1001, which lets its entrypoint fix the two things below automatically.

Docker socket: Most services, such as S3, SQS and DynamoDB, run inside Floci itself and need nothing extra. Floci emulates Lambda, ECR, RDS and a few others by starting containers, which requires access to the host's /var/run/docker.sock. As the image does not start as root, it cannot add the socket's group itself, so pass it with --group-add (on Linux hosts):

docker run -d -p 4566:4566 \
  -v /var/run/docker.sock:/var/run/docker.sock \
  --group-add "$(stat -c %g /var/run/docker.sock)" \
  cgr.dev/ORGANIZATION/floci:latest

Alternatively, start the container with --user 0, as upstream does: the entrypoint adds the socket's group, then drops to UID 1001.

Bind mounts: With any storage mode other than memory, a host directory bind-mounted at /app/data must be writable by UID 1001, or Floci refuses to start. Run chown 1001:0 on the host directory, or start the container with --user 0: the entrypoint then fixes the ownership and drops to UID 1001. Named volumes work as-is.

Runtime: Upstream's image runs Floci as a GraalVM native binary. This image runs the same Floci release on a JVM; the services, APIs and configuration are unchanged.

Getting Started

To start the emulator on the default edge port, run:

docker run --rm -d -p 4566:4566 --name floci cgr.dev/ORGANIZATION/floci:latest

Then point any AWS SDK or CLI at http://localhost:4566:

AWS_ACCESS_KEY_ID=test AWS_SECRET_ACCESS_KEY=test AWS_DEFAULT_REGION=us-east-1 \
  aws --endpoint-url http://localhost:4566 s3 mb s3://my-bucket

To persist state across restarts, stop the container above (docker stop floci), then enable persistent storage and mount a volume at /app/data:

docker run --rm -d -p 4566:4566 \
  -e FLOCI_STORAGE_MODE=persistent \
  -v floci-data:/app/data \
  cgr.dev/ORGANIZATION/floci:latest

Documentation and Resources

• Floci installation
• Floci quick start
• Floci on GitHub

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.