ruby
Runtime · Language runtime · standard · v3.4.10
Hardened Ruby interpreter with Bundler, a base image to FROM for Ruby apps. Latest 3 stable lines (3.2/3.3/3.4).
Security report (Trivy)
Security report (Trivy) · ruby 3.4.10
Published versions
1 tagEach tag is a multi-arch index (amd64 + arm64) pinned by digest. Tagged by version, never :latest.
| Version | Size | Published | Digest |
|---|---|---|---|
| 3.4.10latest | 46.8 MB | 2026-07-28 | sha256:c4b1d95136fe… |
Use it as a base image
Reference it in the FROM line of your Dockerfile. Nonroot, read-only root filesystem, built for amd64 and arm64.
FROM ghcr.io/quenchworks/images/ruby:3.4.10Or pull it directly
docker pull ghcr.io/quenchworks/images/ruby:3.4.10- Version line
- 3.4.10
- Latest line
- 3.4.10
- Architectures
- amd64, arm64
- Runs as
- nonroot (uid 1001)
- Root filesystem
- read-only
- License
- Ruby
Verify the supply chain
This image is cosign-signed and carries an SPDX SBOM and a SLSA build-provenance attestation on the same digest. Check all three before you build on it:
# 1. signature — built and signed by QuenchWorks CI
cosign verify ghcr.io/quenchworks/images/ruby:3.4.10 \
--certificate-identity-regexp 'https://github.com/quenchworks/.+' \
--certificate-oidc-issuer https://token.actions.githubusercontent.com
# 2. SLSA build provenance — which workflow built it, from what
cosign verify-attestation --type https://slsa.dev/provenance/v1 ghcr.io/quenchworks/images/ruby:3.4.10 \
--certificate-identity-regexp 'https://github.com/quenchworks/.+' \
--certificate-oidc-issuer https://token.actions.githubusercontent.com
# 3. SPDX SBOM — the package inventory
cosign verify-attestation --type https://spdx.dev/Document/v2.3 ghcr.io/quenchworks/images/ruby:3.4.10 \
--certificate-identity-regexp 'https://github.com/quenchworks/.+' \
--certificate-oidc-issuer https://token.actions.githubusercontent.comSee the SBOM & provenance guide for reading the SBOM and using these checks in CI.
Best-practice Dockerfile for 3.4.10
Install gems with Bundler in deployment mode in the build stage, then copy the vendored bundle and app onto a clean ruby base. Native gem build tooling stays behind.
# Build stage: install gems in deployment mode (build deps included).FROM ghcr.io/quenchworks/images/ruby:3.4.10 AS buildUSER rootWORKDIR /appENV BUNDLE_PATH=/app/vendor/bundle \ BUNDLE_DEPLOYMENT=true \ BUNDLE_WITHOUT=development:test
COPY Gemfile Gemfile.lock ./RUN ["bundle", "install"]COPY . .
# Runtime stage: copy the vendored bundle + app onto a clean ruby base.FROM ghcr.io/quenchworks/images/ruby:3.4.10 AS runtimeWORKDIR /appENV BUNDLE_PATH=/app/vendor/bundle \ BUNDLE_DEPLOYMENT=true \ BUNDLE_WITHOUT=development:test \ GEM_HOME=/tmp/gemCOPY --from=build /app /appUSER 1001EXPOSE 3000CMD ["bundle", "exec", "ruby", "app.rb"]This Dockerfile is pinned to the 3.4.10 line. For the line-by-line walkthrough and ecosystem variants (npm/Yarn, pip/uv/Poetry, Maven/Gradle), see the Build hardened imagesguide.
Upstream project: https://github.com/ruby/ruby