docs: record Gitea registry authentication blocker
This commit is contained in:
@@ -19,9 +19,35 @@
|
||||
|
||||
仍需完成:
|
||||
|
||||
- 将 Havline 多架构镜像推送到 Gitea 容器仓库;
|
||||
- 修复 Gitea Registry 的 HTTP token realm,使 Docker 能正常 push/pull;
|
||||
- 确认飞牛设备是否可以匿名拉取,或在安装前配置 Registry 登录;
|
||||
- 在飞牛测试设备验证安装、启动、入口、升级和卸载;
|
||||
- 验证 amd64 与 arm64 镜像均可用。
|
||||
- 验证 amd64 与 arm64 镜像均可在真实设备上拉取。
|
||||
|
||||
## 当前阻塞
|
||||
|
||||
`jayhub.top/mrlee/havline:1.9.0` 已经包含 amd64 与 arm64 多架构索引,
|
||||
但当前 Gitea 返回的认证地址仍是 HTTP:
|
||||
|
||||
```text
|
||||
WWW-Authenticate: Bearer realm="http://jayhub.top/v2/token", ...
|
||||
```
|
||||
|
||||
Docker 会在 HTTP 到 HTTPS 的跳转过程中丢失换取 token 所需的认证信息,
|
||||
因此 `docker pull` 和 `docker push` 都会报:
|
||||
|
||||
```text
|
||||
failed to fetch oauth token:
|
||||
authorization server did not include a token in the response
|
||||
```
|
||||
|
||||
在 Gitea `ROOT_URL` 改成 `https://jayhub.top/` 并确认反向代理传递
|
||||
`X-Forwarded-Proto: https` 之前,飞牛设备无法稳定拉取该镜像。
|
||||
详细修复步骤见主程序仓库:
|
||||
|
||||
```text
|
||||
docs/gitea-registry-fix.md
|
||||
```
|
||||
|
||||
## 镜像地址
|
||||
|
||||
|
||||
Reference in New Issue
Block a user