gocd/gocd-agent-wolfiGoCD agent container image based on Wolfi latest.
Please make sure to log them at [***]
Start the container with this:
docker run -d -e GO_SERVER_URL=... gocd/gocd-agent-wolfi:v25.4.0
Note: Please make sure to always provide the version. We do not publish the latest tag. And we don't intend to.
This will start the GoCD agent and connect it the GoCD server specified by GO_SERVER_URL.
Note: The
GO_SERVER_URLmust be an HTTPS url and end with/go, for e.g.[***]
If you have a gocd-server container running and it's named angry_feynman, you can connect a gocd-agent container to it by doing:
docker run -d -e GO_SERVER_URL=[***] inspect --format='{{(index (index .NetworkSettings.IPAddress))}}' angry_feynman):8153/go gocd/gocd-agent-wolfi:v25.4.0
OR
If the docker container running the GoCD server has ports mapped to the host,
docker run -d -e GO_SERVER_URL=[***] inspect --format='{{(index (index .NetworkSettings.Ports "8153/tcp") 0).HostPort}}' angry_feynman)/go gocd/gocd-agent-wolfi:v25.4.0
docker run -d \ -e AGENT_AUTO_REGISTER_KEY=... \ -e AGENT_AUTO_REGISTER_RESOURCES=... \ -e AGENT_AUTO_REGISTER_ENVIRONMENTS=... \ -e AGENT_AUTO_REGISTER_HOSTNAME=... \ gocd/gocd-agent-wolfi:v25.4.0
If the AGENT_AUTO_REGISTER_* variables are provided (we recommend that you do), then the agent will be automatically approved by the server. See the auto registration docs on the GoCD website.
To configure SSL parameters, pass the parameters using the environment variable AGENT_BOOTSTRAPPER_ARGS. See this documentation for supported options.
shelldocker run -d \ -e AGENT_BOOTSTRAPPER_ARGS='-sslVerificationMode NONE ...' \ gocd/gocd-agent-wolfi:v25.4.0
This image will work well with the docker elastic agent plugin and the docker swarm elastic agent plugin. No special configuration would be needed.
The GoCD agent will store all configuration, logs and perform builds in /godata. If you'd like to provide secure credentials like SSH private keys among other things, you can mount /home/go.
docker run -v /path/to/godata:/godata -v /path/to/home-dir:/home/go gocd/gocd-agent-wolfi:v25.4.0
Note: Ensure that
/path/to/home-dirand/path/to/godatais accessible by thegouser in container (gouser - uid 1000).
JVM options can be tweaked using the environment variable GOCD_AGENT_JVM_OPTS.
docker run -e GOCD_AGENT_JVM_OPTS="-Dfoo=bar" gocd/gocd-agent-wolfi:v25.4.0
The GoCD server runs as the go user, the location of the various directories is:
| Directory | Description |
|---|---|
/godata/config | the directory where the GoCD configuration is stored |
/godata/pipelines | the directory where the agent will run builds |
/godata/logs | the directory where GoCD logs will be written out to |
/home/go | the home directory for the GoCD server |
To be able to run the docker and docker-compose commands inside your jobs, you will need to share the docker socket as a volume from your host which is pretty classic.
In this case, as the docker deamon will be the one mounting the volumes you define, the path to the files you will want to mount (basically inside /godata/pipelines) need to be the same so that the docker deamon (which is running on the host) can find the files.
If you run several agents container, you will need to overwrite the VOLUME_DIR environment variable to have a different path for your /godata for each of your GoCD agent containers (to avoid issues). For example, if the volume on your host for the first container is /go-agent1/godata, you will set the VOLUME_DIR environment data on your container to /go-agent1/godata and the docker-entrypoint.sh script will automatically manage it and make sure the agent stores its configuration, logs and pipelines there.
docker ps -adocker logs CONTAINER_IDdocker exec -it CONTAINER_ID /bin/bash, then run less /godata/logs/*.log inside the container.plainCopyright Thoughtworks, Inc. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at [***] Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
通过 Docker 登录认证访问私有仓库
在 Linux 系统配置镜像服务
在 Docker Desktop 配置镜像
Docker Compose 项目配置
Kubernetes 集群配置 Containerd
K3s 轻量级 Kubernetes 镜像加速
VS Code Dev Containers 配置
MacOS OrbStack 容器配置
在宝塔面板一键配置镜像
Synology 群晖 NAS 配置
飞牛 fnOS 系统配置镜像
极空间 NAS 系统配置服务
爱快 iKuai 路由系统配置
绿联 NAS 系统配置镜像
QNAP 威联通 NAS 配置
Podman 容器引擎配置
HPC 科学计算容器配置
ghcr、Quay、nvcr 等镜像仓库
无需登录使用专属域名
需要其他帮助?请查看我们的 常见问题Docker 镜像访问常见问题解答 或 提交工单
免费版仅支持 Docker Hub 访问,不承诺可用性和速度;专业版支持更多镜像源,保证可用性和稳定速度,提供优先客服响应。
专业版支持 docker.io、gcr.io、ghcr.io、registry.k8s.io、nvcr.io、quay.io、mcr.microsoft.com、docker.elastic.co 等;免费版仅支持 docker.io。
当返回 402 Payment Required 错误时,表示流量已耗尽,需要充值流量包以恢复服务。
通常由 Docker 版本过低导致,需要升级到 20.x 或更高版本以支持 V2 协议。
先检查 Docker 版本,版本过低则升级;版本正常则验证镜像信息是否正确。
使用 docker tag 命令为镜像打上新标签,去掉域名前缀,使镜像名称更简洁。
来自真实用户的反馈,见证轩辕镜像的优质服务