Did caddy:2.4.1 docker image drop the support for arm64?

1. Caddy version (caddy version):

caddy:2.4.1-builder docker image

2. How I run Caddy:

a. System environment:

ubuntu-18.04

b. Command:

Github actions are used to build a docker image that has caddy-builder as its base image

jobs:
  docker_image:
    name: Docker image test and publishing
    runs-on: ubuntu-18.04
    steps:
      - uses: actions/checkout@v2

      - name: Set up QEMU
        uses: docker/setup-qemu-action@v1

      - name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v1

      - name: Build a multi-platform docker image and push
        uses: docker/build-push-action@v2
        with:
          platforms: linux/amd64,linux/arm64
          cache-to: mode=max,type=inline
          load: false
          push: ${{ github.repository_owner == 'femiwiki' && github.ref == 'refs/heads/main' }}
          tags: |
            ghcr.io/femiwiki/mediawiki:latest

* This is not the full workflow file.

c. Dockerfile

FROM --platform=$TARGETPLATFORM caddy:2.4.1-builder
ARG CADDY_MWCACHE_VERSION=0.0.1

RUN xcaddy build \
      --with github.com/caddy-dns/route53 \
      --with "github.com/femiwiki/caddy-mwcache@v${CADDY_MWCACHE_VERSION}"

* This is not the full dockerfile.

3. The problem I’m having:

Building a docker image using the above dockerfile falis

4. Error messages and/or full log output:

error: failed to solve: rpc error: code = Unknown desc = failed to solve with frontend dockerfile.v0: failed to create LLB definition: no match for platform in manifest sha256:822d98703fed6c19456bda86af28b0595669751d21587809428b412157ad3621: not found
Error: buildx call failed with: error: failed to solve: rpc error: code = Unknown desc = failed to solve with frontend dockerfile.v0: failed to create LLB definition: no match for platform in manifest sha256:822d98703fed6c19456bda86af28b0595669751d21587809428b412157ad3621: not found

5. Links to relevant resources:

If it did, it wasn’t intentional. I think it might still be stuck in Docker’s Jenkins build server’s queue :thinking:

It was just merged yesterday (see caddy: v2.4.1 release by hairyhenderson · Pull Request #10211 · docker-library/official-images · GitHub), and it seems like the build server goes somewhat slowly at times. See the sidebar, there’s still some jobs queued up for caddy. (But I find Jenkins super hard to navigate so I can’t really figure out how to tell which image variants are still in the queue)

https://doi-janky.infosiftr.net/job/repo-info/job/local/

/cc @hairyhenderson

1 Like

Now it is provided, thank you

1 Like

This topic was automatically closed after 30 days. New replies are no longer allowed.