
!https://raw.githubusercontent.com/11notes/static/refs/heads/master/img/banner/README.png
!size!https://raw.githubusercontent.com/11notes/static/refs/heads/master/img/markdown/transparent5x2px.png!pulls!https://raw.githubusercontent.com/11notes/static/refs/heads/master/img/markdown/transparent5x2px.png%5B](https://github.com/11notes/docker-go/issues)!https://raw.githubusercontent.com/11notes/static/refs/heads/master/img/markdown/transparent5x2px.png!swiss_made
Build go apps with the default tooling present
What can I do with this? Build go applications with the default tooling present.
yamlFROM 11notes/go:1.24 RUN set -ex; \ git clone https://github.com/some/repo; \ cd ./repo; \ go build -ldflags="-extldflags=-static" -o repo main.go;
| Parameter | Value | Description |
|---|---|---|
user | docker | user name |
uid | 1000 | user identifier |
gid | 1000 | group identifier |
home | /go | home directory of user docker |
| Parameter | Value | Default |
|---|---|---|
TZ | Time Zone | |
DEBUG | Will activate debug option for container image and app (if available) |
These are the main tags for the image. There is also a tag for each commit and its shorthand sha256 value.
It is my opinion that the :latest tag is a bad habbit and should not be used at all. Many developers introduce breaking changes in new releases. This would messed up everything for people who use :latest. If you don’t want to change the tag to the latest semver, simply use the short versions of semver. Instead of using :1.26.3 you can use :1 or :1.26. Since on each new version these tags are updated to the latest version of the software, using them is identical to using :latest but at least fixed to a major or minor version. Which in theory should not introduce breaking changes.
If you still insist on having the bleeding edge release of this app, simply use the :rolling tag, but be warned! You will get the latest version of the app instantly, regardless of breaking changes or security issues or what so ever. You do this at your own risk!
docker pull 11notes/go:1.26.3 docker pull ghcr.io/11notes/go:1.26.3 docker pull quay.io/11notes/go:1.26.3
This image is provided to you at your own risk. Always make backups before updating an image to a different version. Check the https://github.com/11notes/docker-go/releases for breaking changes. If you have any problems with using this image simply raise an https://github.com/11notes/docker-go/issues, thanks. If you have a question or inputs please create a new https://github.com/11notes/docker-go/discussions instead of an issue. You can find all my other repositories on https://github.com/11notes?tab=repositories.
created 11.05.2026, 14:53:27 (CET)
以下是 11notes/go 相关的常用 Docker 镜像,适用于 不同场景 等不同场景:
您可以使用以下命令拉取该镜像。请将 <标签> 替换为具体的标签版本。如需查看所有可用标签版本,请访问 标签列表页面。

探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
通过 Docker 登录认证访问私有仓库
无需登录使用专属域名
Kubernetes 集群配置 Containerd
K3s 轻量级 Kubernetes 镜像加速
VS Code Dev Containers 配置
Podman 容器引擎配置
HPC 科学计算容器配置
ghcr、Quay、nvcr 等镜像仓库
Harbor Proxy Repository 对接专属域名
Portainer Registries 加速拉取
Nexus3 Docker Proxy 内网缓存
需要其他帮助?请查看我们的 常见问题Docker 镜像访问常见问题解答 或 提交工单
docker search 限制
站内搜不到镜像
离线 save/load
插件要用 plugin install
WSL 拉取慢
安全与 digest
新手拉取配置
镜像合规机制
不支持 push
manifest unknown
no matching manifest(架构)
invalid tar header(解压)
TLS 证书失败
DNS 超时
域名连通性排查
410 Gone 排查
402 与流量用尽
401 认证失败
429 限流
D-Bus 凭证提示
413 与超大单层
来自真实用户的反馈,见证轩辕镜像的优质服务