packaged by Chainguard
Contact our team to test out this image for free. Please also indicate any other images you would like to evaluate.
A minimal wolfi-based image for SFTPGo, a full-featured and highly configurable SFTP, HTTP/S, FTP/S and WebDAV server
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 Chainguard Image for SFTPGo is meant to serve as a drop-in replacement for the official SFTPGo image. Like most other Chainguard Images, this image has few-to-zero CVEs and does not run as the root user.
The image runs as the non-root sftpgo user (UID/GID 1000), matching the upstream image. Key filesystem locations:
| Path | Purpose |
|---|---|
| Default configuration file |
| Working directory and default data provider location (bolt) |
| Users' base directory |
| Data provider backups |
| Bundled |
By default the server logs to stdout (SFTPGO_LOG_FILE_PATH="").
Tags with a -plugins suffix (for example plugins and 2-plugins) correspond to upstream's -plugins tags. They add the official SFTPGo plugins (auth, eventsearch, eventstore, geoipfilter, kms and pubsub) and jq. As upstream does, the variant ships the plugins without enabling any of them; configure the ones you need at runtime.
Each plugin is installed as /usr/bin/sftpgo-plugin-<name> and is also reachable at the upstream path /usr/local/bin/sftpgo-plugin-<name>, so plugin configuration written for the upstream image works unchanged.
Run SFTPGo with Docker, exposing the SFTP (2022) and Web Admin / REST API (8080) ports:
The Web Admin interface is then available at http://localhost:8080.
To persist data across restarts, mount volumes for the data and state directories:
To authenticate users against LDAP or Active Directory, run a -plugins tag and enable the auth plugin. Settings prefixed SFTPGO_PLUGIN_AUTH_ are passed through to the plugin. This example connects over LDAPS and trusts the directory's CA certificate, mounted from ldap-ca.pem:
The plugin sends the bind password and users' passwords to the directory, so keep the connection encrypted. AUTO_MTLS=1 protects only the connection between SFTPGo and the plugin. To use StartTLS on port 389 instead of LDAPS, set SFTPGO_PLUGIN_AUTH_LDAP_URL=ldap://ldap.example.com:389 and SFTPGO_PLUGIN_AUTH_STARTTLS=1; without STARTTLS=1, an ldap:// URL is unencrypted. Omit CA_CERTIFICATES when the directory's certificate chains to a public CA.
SCOPE=5 applies the plugin to password and keyboard-interactive logins. See the auth plugin documentation for group mapping and other options.
For configuration options, storage backends and deployment guidance, see the upstream SFTPGo documentation.
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:
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.
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.
Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.
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's container images contain software packages that are direct or transitive dependencies. The following licenses were found in the "latest" tag of this image:
For a complete list of licenses, please refer to this Image's SBOM.
Software license agreementChainguard Containers are SLSA Level 3 compliant with detailed metadata and documentation about how it was built. We generate build provenance and a Software Bill of Materials (SBOM) for each release, with complete visibility into the software supply chain.
SLSA compliance at ChainguardThis image helps reduce time and effort in establishing PCI DSS 4.0 compliance with low-to-no CVEs.
PCI DSS at Chainguard