Skip to content

Caddy dockerhub repo appears out of sync #416

@thundernode

Description

@thundernode

I was troubleshooting a failing build today when trying to update to 2.10.2 (wrong Go version).

partial build log
[1/2] STEP 2/3: ARG HE_VERSION DP_VERSION APP_VERSION
--> Using cache 4bf0a814f81714f41a6b05367971beda3b36cb320430b5b529c094db9ed1bdd9
--> 4bf0a814f817
[1/2] STEP 3/3: RUN XCADDY_DEBUG=1 xcaddy build v${APP_VERSION}     --with github.com/lucaslorentz/caddy-docker-proxy/v2@v$DP_VERSION     --with github.com/caddy-dns/he@v$HE_VERSION
2025/08/23 19:52:02 [INFO] absolute output file path: /usr/bin/caddy
2025/08/23 19:52:02 [INFO] Temporary folder: /tmp/buildenv_2025-08-23-1952.3707817347
2025/08/23 19:52:02 [INFO] Writing main module: /tmp/buildenv_2025-08-23-1952.3707817347/main.go
package main

import (
        caddycmd "github.com/caddyserver/caddy/v2/cmd"

        // plug in Caddy modules here
        _ "github.com/caddyserver/caddy/v2/modules/standard"
        _ "github.com/lucaslorentz/caddy-docker-proxy/v2"
        _ "github.com/caddy-dns/he"
)

func main() {
        caddycmd.Main()
}
2025/08/23 19:52:02 [INFO] Initializing Go module
2025/08/23 19:52:02 [INFO] exec (timeout=0s): /usr/local/go/bin/go mod init caddy
go: creating new go.mod: module caddy
go: to add module requirements and sums:
        go mod tidy
2025/08/23 19:52:02 [INFO] Pinning versions
2025/08/23 19:52:02 [INFO] exec (timeout=0s): /usr/local/go/bin/go get -v github.com/caddyserver/caddy/v2@v2.10.2
go: downloading github.com/caddyserver/caddy/v2 v2.10.2
go: github.com/caddyserver/caddy/v2@v2.10.2 requires go >= 1.25 (running go 1.24.6; GOTOOLCHAIN=local)
2025/08/23 19:52:03 [FATAL] exit status 1

I moved to trying to pull the builder image from docker.io/caddy to docker.io/caddy/caddy as a sanity test, it built just fine.

partial build log

[1/2] STEP 1/3: FROM docker.io/caddy/caddy:2.10-builder-alpine AS builder
Trying to pull docker.io/caddy/caddy:2.10-builder-alpine...
Getting image source signatures
Copying blob be4f1c944bfe done   |
Copying blob 8286cb4ece30 done   |
Copying blob ec7d4ca09441 done   |
Copying blob 18414ed0f666 done   |
Copying blob 4f4fb700ef54 skipped: already exists
Copying blob 9824c27679d3 skipped: already exists
Copying blob 4a1d187e818b done   |
Copying blob 90a0d7e229ea done   |
Copying config d45f0dd47f done   |
Writing manifest to image destination
[1/2] STEP 2/3: ARG HE_VERSION DP_VERSION APP_VERSION
--> 12e23a89914a
[1/2] STEP 3/3: RUN XCADDY_DEBUG=1 xcaddy build v${APP_VERSION}     --with github.com/lucaslorentz/caddy-docker-proxy/v2@v$DP_VERSION     --with github.com/caddy-dns/he@v$HE_VERSION
2025/08/23 19:52:42 [INFO] absolute output file path: /usr/bin/caddy
2025/08/23 19:52:42 [INFO] Temporary folder: /tmp/buildenv_2025-08-23-1952.3413518751
2025/08/23 19:52:42 [INFO] Writing main module: /tmp/buildenv_2025-08-23-1952.3413518751/main.go
package main

import (
        caddycmd "github.com/caddyserver/caddy/v2/cmd"

        // plug in Caddy modules here
        _ "github.com/caddyserver/caddy/v2/modules/standard"
        _ "github.com/lucaslorentz/caddy-docker-proxy/v2"
        _ "github.com/caddy-dns/he"
)

func main() {
        caddycmd.Main()
}
2025/08/23 19:52:42 [INFO] Initializing Go module
2025/08/23 19:52:42 [INFO] exec (timeout=0s): /usr/local/go/bin/go mod init caddy
go: creating new go.mod: module caddy
go: to add module requirements and sums:
        go mod tidy
2025/08/23 19:52:42 [INFO] Pinning versions
2025/08/23 19:52:42 [INFO] exec (timeout=0s): /usr/local/go/bin/go get -v github.com/caddyserver/caddy/v2@v2.10.2
go: downloading github.com/caddyserver/caddy/v2 v2.10.2
go: downloading github.com/caddyserver/certmagic v0.24.0
go: downloading github.com/cespare/xxhash/v2 v2.3.0
go: downloading github.com/google/uuid v1.6.0
go: downloading github.com/prometheus/client_golang v1.23.0
go: downloading github.com/quic-go/quic-go v0.54.0
go: downloading go.uber.org/zap v1.27.0

When i checked https://hub.docker.com/_/caddy i noticed the images there had last been updated 11 days ago, explaining why they wouldn't have the new Go Version required to build 2.10.1/2.

I'm not sure if I'm just adopting too early or if what updates the official images has stopped.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions