goreleaser

The official GoReleaser image — release automation for Go projects that builds binaries, archives, packages, and container images and publishes them to GitHub, registries, and package managers.

goreleaser, go release, release automation, go binaries, ci/cd, packaging

What is GoReleaser?

The GoReleaser image packages GoReleaser, a release automation tool for Go projects that cross-compiles binaries for multiple platforms and produces archives, Linux packages, Homebrew formulas, SBOMs, signatures, checksums, and container images from a single .goreleaser.yaml configuration. It then publishes the results to GitHub or GitLab releases, container registries, and package repositories. The image is typically run as a step in CI pipelines such as GitHub Actions, GitLab CI, and Jenkins, often with the Go toolchain and Docker or Buildx available in the job. It is used by open-source maintainers and DevOps teams that want consistent, repeatable releases of Go software.

What is Echo's GoReleaser image?

Echo's GoReleaser image is a hardened build of GoReleaser on Echo's hardened base. Echo images are designed to be a drop-in replacement: swap the image reference in your Dockerfile or deployment manifest and CVEs go to zero without disrupting your .goreleaser.yaml configuration, signing keys, registry authentication, and release tokens. Every image is tested across clouds, image use cases, and deployment targets. Echo ships every image in two variants:

  • Distroless variant — optimized for runtime use, with the smallest possible attack surface
  • Default variant — includes essential build tools, package managers, and shells for teams that need operational access

For production GoReleaser deployments, the distroless variant keeps all runtime operations — cross-compilation, archiving, packaging, signing, image publishing, and release creation — fully intact while minimizing exposure; the default variant suits DevOps and release engineering teams that need shell access for debugging release configuration, checking snapshots, or inspecting build outputs.

What is the difference between Echo's GoReleaser image and the public GoReleaser image?

Public GoReleaser images ship on bases that include OS-level tooling convenient for development but which contribute CVEs that accumulate on a release tooling image used in production. GoReleaser images run inside CI pipelines and operational jobs with access to source code, release tokens, signing keys, and registry credentials. OS-level CVEs in the base image — particularly in libraries such as openssl, zlib, and libc, git, and the Go toolchain dependencies — create exploitable paths in an environment that application-level controls never see. Because tooling images are pulled and executed constantly across pipelines, they are also a steady source of scanner noise — every package in the base becomes a finding your security team must triage, even when none of it is exercised by the job. Echo's build retains everything GoReleaser needs for cross-compilation, archiving, packaging, signing, image publishing, and release creation while removing the packages that don't belong in a production GoReleaser release tooling image. As we covered in our post on how to protect your company from software supply chain attacks, build and automation images that run with access to source code, credentials, and deployment targets are a high-value path into everything downstream. Echo commits to a 7-day SLA for critical and high severity vulnerabilities, and 10 days for medium, low, and unknown — with vulnerabilities triaged within 24 hours. Echo images are recognized by all major scanners and mirrored to all major registries, so they fit into existing pipelines without changing your registry, scanner, or runtime tooling.

FAQ

Can I replace my GoReleaser image with Echo's GoReleaser image?

Yes. Echo's GoReleaser image is a drop-in replacement. Update the FROM line in your Dockerfile and your workloads keep running. .goreleaser.yaml settings, GitHub or GitLab tokens, cosign signing, Docker publishing, and CI workflow steps all continue to work without changes to your release configuration.

Is Echo's GoReleaser image FIPS-validated?

Yes. Echo's FIPS-validated images use cryptographic modules with an active FIPS 140-3 CMVP certificate, making them fit for federal use — unlike FIPS-compliant images that haven't been validated. This matters for teams running GoReleaser workloads inside FedRAMP boundaries, where a release tooling image that builds and publishes release artifacts using powerful credentials must meet cryptographic requirements across the full stack — including the OpenSSL and TLS libraries bundled with the GoReleaser image.

What is Echo's vulnerability management SLA on the GoReleaser image?

Echo commits to a 7-day SLA for critical and high severity vulnerabilities, and 10 days for medium, low, and unknown — with vulnerabilities triaged within 24 hours. Patches are mirrored automatically into your private registry so you're always running a clean version — critical for a tooling image that is pulled and run constantly across pipelines with access to source code, release tokens, signing keys, and registry credentials.

Is Echo's GoReleaser image distroless?

Echo ships every image in two variants: a distroless variant optimized for runtime use, and a default variant that includes essential build tools, package managers, and shells. For production GoReleaser deployments, the distroless variant is the leaner, more secure choice; for DevOps and release engineering teams that need shell access for debugging release configuration, checking snapshots, or inspecting build outputs, the default variant is the right fit.

How does Echo achieve such a drastic CVE reduction in GoReleaser?

Echo's GoReleaser image is built from source with only the absolute essentials needed to run the GoReleaser release tooling image, which significantly shrinks the attack surface. Echo also patches aggressively over time, with backports available so you can stay on the GoReleaser version your applications and their dependencies are certified against — avoiding a disruptive upgrade forced purely by OS-level vulnerabilities in the base image rather than by your own requirements.

Will Echo's GoReleaser image help us achieve FedRAMP?

Yes. The hard parts of FedRAMP — managing vulnerabilities, applying fixes, and using FIPS-validated cryptography — are baked into Echo images, including STIG-hardened configuration and ConMon/POA&M-ready reporting. For DevOps and release engineering teams running GoReleaser under an ATO — whether that's signed binary releases, container image publishing, or release pipelines for internal Go tooling — Echo's hardened GoReleaser image keeps the release tooling image layer in-boundary and compliant without requiring custom hardening scripts or manual base image patching between compliance cycles.

‍

Interested in base images that start and stay clean?