Last changed
docker pull cgr.dev/chainguard/hugo
Need access to a specific tag? Contact us.
Be the first to hear about exciting product updates, critical vulnerability alerts, compare alternative images, and more.
Sign UpThis is a minimal Hugo image.
Chainguard Containers are regularly-updated, secure-by-default container images.
For those with access, this container image is available on cgr.dev
:
Be sure to replace the ORGANIZATION
placeholder with the name used for your organization's private repository within the Chainguard Registry.
The following is an example of using the Hugo image locally. It's based on the official Hugo "quickstart" example.
To begin, start a shell in the Hugo developer (dev) container.
Create a new Hugo site using the quickstart commands.
Navigate into the new site's root directory.
Initiate an empty Git repository
Clone a Hugo theme into the themes
directory.
Add a line to the site's configuration file to let Hugo know to use the new theme.
Start the Hugo development server to serve the site. Be sure to change the default bind address and port to make the site accessible outside of the container.
Now open your browser to localhost:8080 to visit the sample site.
When finished, you can press CTRL + C
to stop the Hugo server from running, and then CTRL + D
to exit the container shell.
If you're interested in enterprise support, SLAs, and access to older tags, get in touch.
Chainguard Containers are minimal container images that are secure by default.
In many cases, the Chainguard Containers tagged as :latest
contain only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager. Chainguard Containers are built with Wolfi, our Linux undistro designed to produce container images that meet the requirements of a more secure software supply chain.
The main features of Chainguard Containers include:
For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a -dev
variant.
Although the -dev
container image variants have similar security features as their more minimal versions, they feature additional software that is typically not necessary in production environments. We recommend using multi-stage builds to leverage the -dev
variants, copying application artifacts into a final minimal container that offers a reduced attack surface that won’t allow package installations or logins.
To better understand how to work with Chainguard Containers, please visit Chainguard Academy and Chainguard Courses.
In addition to Containers, Chainguard offers VMs and Libraries. Contact Chainguard to access additional products.
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.
Chainguard container images contain software packages that are direct or transitive dependencies. The following licenses were found in the "latest" tag of this image:
Apache-2.0
GCC-exception-3.1
GPL-3.0-or-later
LGPL-2.1-or-later
MIT
MPL-2.0
For a complete list of licenses, please refer to this Image's SBOM.
Software license agreementA FIPS validated version of this image is available for FedRAMP compliance. STIG is included with FIPS image.