惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

WordPress大学
WordPress大学
阮一峰的网络日志
阮一峰的网络日志
Jina AI
Jina AI
博客园 - Franky
U
Unit 42
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
宝玉的分享
宝玉的分享
B
Blog RSS Feed
雷峰网
雷峰网
D
DataBreaches.Net
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
I
InfoQ
美团技术团队
云风的 BLOG
云风的 BLOG
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
Martin Fowler
Martin Fowler
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
大猫的无限游戏
大猫的无限游戏
G
Google Developers Blog
T
Tailwind CSS Blog
P
Proofpoint News Feed
The GitHub Blog
The GitHub Blog
月光博客
月光博客
Engineering at Meta
Engineering at Meta

皓子的小站

网站字体应用之坑——font-family 篇 糟糕的 meta name="theme-color" How to Automatically Track Newly Supported ESLint Rules in Oxlint How to Gradually Migrate from ESLint to Oxlint (Without Breaking Everything) 静态资源预压缩:零运行时开销,极致节省带宽 CVE-2025-70886 Proof of Concept (PoC) | A Script to Crash Halo CMS Comment Backend 自定义网页鼠标指针——一段曲折的旅程 CVE-2025-70886 漏洞复现/PoC | 一个脚本让 Halo CMS 评论后台瘫痪 2025 年终总结 & 博客两周年 老用户专享!已有 Halo 专业版授权可免费升级商业版 自动追踪 Oxlint 对 ESLint 规则的新增支持 Halo 贡献者证书与实体周边盲盒开箱 博客评论系统指南 CDN 回源跟随配置导致登录异常问题排查 SCDN 免费赞助计划:助力高质量博客&博客圈 锐捷校园网:网络共享与带宽叠加方案(哈理工案例) ESLint 到 Oxlint 渐进式迁移快速上手指南 Fixing Vite Breaking Inline JS & CSS in Thymeleaf Templates 解决 Vite 破坏 Thymeleaf 模板内联 JS & CSS 的方法 我的博客,为什么是月更? 博客俱乐部一周年纪念品开箱 网站字体加载之坑——format 篇 经历 1000000000 次 DDoS 请求攻击后,我总结了三条经验 题解分享:[AtCoder Beginner Contest 414 E] Count A%B=C 题解分享:[蓝桥杯 2025 国 Python A] 杨辉三角 P12876 FiF口语训练破解刷分教程(适用于 Windows) 不要与蠢人辩论 小心网络地雷·续篇 当心网络组织“开往”·续篇 当心网络组织“开往”
Fixing GitHub Actions push to ghcr '403 Forbidden&ap...
HowieHz · 2024-11-19 · via 皓子的小站

此文章有中文版本/This article is available in Chinese

Phenomenon

The GitHub Action workflow setup looks like this:

Screenshot of the GitHub Action workflow setup

When running it, the following error occurs:

Error screenshot showing a 403 Forbidden issue

Solution

Everything worked fine during the initial build. However, when I re-cloned the repository and attempted to build it again while preparing a tutorial, I kept encountering a 403 error. After a lengthy search, I finally found the solution.

Original discussion link: Random 403 errors when pushing to GHCR · Issue #463 · docker/build-push-action (github.com)

Adjust Settings on GitHub

Access the following URL:
https://github.com/orgs/[XXX]/packages/container/[YYY]/settings

Replace [XXX] with your GitHub username and [YYY] with the project name.
For instance, after forking the repository, my repo is HowieHz/umami, so I accessed:
https://github.com/orgs/HowieHz/packages/container/umami/settings

Screenshot showing the GitHub package settings page

Fix the Permissions

Following onedr0p's instructions:

  1. Click on Add Repository to include your repository.
  2. Set the rule to Write or Admin.

After these changes, the issue should be resolved.

To make searching easier, this article and the one linked above were extracted from the following article:
Addressing the Umami Active API Latency Issue