[PR #541] [MERGED] Create a Workflow for publishing ARM Docker Images #1216

New issue

Closed

opened 2026-03-01 14:48:53 +03:00 by kerem · 0 comments

kerem commented

2026-03-01 14:48:53 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/ArchiveBox/ArchiveBox/pull/541
Author: @chrismeller
Created: 11/17/2020
Status: ✅ Merged
Merged: 11/22/2020
Merged by: @pirate

Base: master ← Head: master

📝 Commits (2)

c0b4198 Create Docker Workflow config
244e296 Remove Docker Workflow's scheduled trigger.

📊 Changes

1 file changed (+61 additions, -0 deletions)

View changed files

➕ .github/workflows/docker.yml (+61 -0)

📄 Description

Summary

Creates a Github Actions workflow for creating and publishing Docker images for the ARM CPU architecture (currently arm64 and armv7) on each push to the repository. This enables, among other things, one to directly run the published image on a Raspberry Pi.

You can see the build history in my branch and see the pushed result in my Docker Hub repo.

This workflow could be expanded to include the existing (presumably manually-built) Docker images that are published for amd64 simply by adding it to the list in the "platforms" parameter at the end of the "Build and push" step.

#534, #407, #78

Changes these areas

Changes no areas within the code, just adds the workflow template.

Additional Setup Steps Required

In order for this to run successfully, you'll need to create several secrets (Repo Settings -> Secrets):

DockerUsername - Your Docker Hub username (nikisweeting). This is used for logging in as well as tagging/pushing the image.
DockerPassword - A Personal Access Token generated from your Docker Hub account. (Name at the top -> Account Settings -> Security -> New Access Token)
DockerRepository - Your Docker Hub repository name (archivebox). This is used purely for tagging/pushing the image.

_{🔄 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/ArchiveBox/ArchiveBox/pull/541 **Author:** [@chrismeller](https://github.com/chrismeller) **Created:** 11/17/2020 **Status:** ✅ Merged **Merged:** 11/22/2020 **Merged by:** [@pirate](https://github.com/pirate) **Base:** `master` ← **Head:** `master` --- ### 📝 Commits (2) - [`c0b4198`](https://github.com/ArchiveBox/ArchiveBox/commit/c0b4198eaf6288e8c0eb95fd75579867746d3695) Create Docker Workflow config - [`244e296`](https://github.com/ArchiveBox/ArchiveBox/commit/244e296652fbcac0431be7d5005e889fa12d6f8b) Remove Docker Workflow's scheduled trigger. ### 📊 Changes **1 file changed** (+61 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `.github/workflows/docker.yml` (+61 -0) </details> ### 📄 Description # Summary Creates a Github Actions workflow for creating and publishing Docker images for the ARM CPU architecture (currently arm64 and armv7) on each push to the repository. This enables, among other things, one to directly run the published image on a Raspberry Pi. You can see the build history in my branch and see the pushed result [in my Docker Hub repo](https://hub.docker.com/r/chrismeller/archivebox). This workflow could be expanded to include the existing (presumably manually-built) Docker images that are published for amd64 simply by adding it to the list in the "platforms" parameter at the end of the "Build and push" step. # Related issues #534, #407, #78 # Changes these areas Changes no areas within the code, just adds the workflow template. # Additional Setup Steps Required In order for this to run successfully, you'll need to create several secrets (Repo Settings -> Secrets): - DockerUsername - Your Docker Hub username (nikisweeting). This is used for logging in as well as tagging/pushing the image. - DockerPassword - A Personal Access Token generated from your Docker Hub account. (Name at the top -> Account Settings -> Security -> New Access Token) - DockerRepository - Your Docker Hub repository name (archivebox). This is used purely for tagging/pushing the image. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>