[PR #266] multi arch support with docker buildx for the arm's race #362

New issue

Open

opened 2026-03-13 16:19:51 +03:00 by kerem · 0 comments

kerem commented

2026-03-13 16:19:51 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/acme-dns/acme-dns/pull/266
Author: @lan10rd
Created: 6/29/2021
Status: 🔄 Open

Base: master ← Head: master

📝 Commits (2)

506b4c2 multi arch support with docker buildx for the arm's race
8cdf435 platforms.

📊 Changes

2 files changed (+54 additions, -0 deletions)

View changed files

➕ Dockerfile.buildx (+23 -0)
➕ docker-buildx.sh (+31 -0)

📄 Description

Yo been having my own repo on docker hub for some time i'm at 10k+ pulls for your image! lol all i did was use buildx so i could have arm support, brohan i can't afford anything but raspberry pi's. https://hub.docker.com/repository/docker/lanl0rd/acme

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/acme-dns/acme-dns/pull/266 **Author:** [@lan10rd](https://github.com/lan10rd) **Created:** 6/29/2021 **Status:** 🔄 Open **Base:** `master` ← **Head:** `master` --- ### 📝 Commits (2) - [`506b4c2`](https://github.com/acme-dns/acme-dns/commit/506b4c202f0452434d4ed93e0187ea0f86f0752c) multi arch support with docker buildx for the arm's race - [`8cdf435`](https://github.com/acme-dns/acme-dns/commit/8cdf4358a3750e83e094ee8c80f5cdb9e34f4124) platforms. ### 📊 Changes **2 files changed** (+54 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `Dockerfile.buildx` (+23 -0) ➕ `docker-buildx.sh` (+31 -0) </details> ### 📄 Description Yo been having my own repo on docker hub for some time i'm at 10k+ pulls for your image! lol all i did was use buildx so i could have arm support, brohan i can't afford anything but raspberry pi's. https://hub.docker.com/repository/docker/lanl0rd/acme --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>