Backport #27930 by @lng2020
The bug has been fixed for several months in the
`docker/build-push-action`
The fix commit is
[d8823bfaed](d8823bfaed
)
as the Gitea Actions Doc mentioned too.
Co-authored-by: Nanguan Lin <70063547+lng2020@users.noreply.github.com>
This commit is contained in:
parent
49f82ac4e3
commit
e47b31c691
2 changed files with 0 additions and 62 deletions
|
@ -130,34 +130,3 @@ More details about the `[actions].DEFAULT_ACTIONS_URL` configuration can be foun
|
||||||
|
|
||||||
Context availability is not checked, so you can use the env context on more places.
|
Context availability is not checked, so you can use the env context on more places.
|
||||||
See [Context availability](https://docs.github.com/en/actions/learn-github-actions/contexts#context-availability).
|
See [Context availability](https://docs.github.com/en/actions/learn-github-actions/contexts#context-availability).
|
||||||
|
|
||||||
## Known issues
|
|
||||||
|
|
||||||
### `docker/build-push-action@v4`
|
|
||||||
|
|
||||||
See [act_runner#119](https://gitea.com/gitea/act_runner/issues/119#issuecomment-738294).
|
|
||||||
|
|
||||||
`ACTIONS_RUNTIME_TOKEN` is a random string in Gitea Actions, not a JWT.
|
|
||||||
But the `docker/build-push-action@v4` tries to parse the token as JWT and doesn't handle the error, so the job fails.
|
|
||||||
|
|
||||||
There are two workarounds:
|
|
||||||
|
|
||||||
Set the `ACTIONS_RUNTIME_TOKEN` to empty manually, like:
|
|
||||||
|
|
||||||
``` yml
|
|
||||||
- name: Build and push
|
|
||||||
uses: docker/build-push-action@v4
|
|
||||||
env:
|
|
||||||
ACTIONS_RUNTIME_TOKEN: ''
|
|
||||||
with:
|
|
||||||
...
|
|
||||||
```
|
|
||||||
|
|
||||||
The bug has been fixed in a newer [commit](https://gitea.com/docker/build-push-action/commit/d8823bfaed2a82c6f5d4799a2f8e86173c461aba?style=split&whitespace=show-all#diff-1af9a5bdf96ddff3a2f3427ed520b7005e9564ad), but it has not been released. So you could use the latest version by specifying the branch name, like:
|
|
||||||
|
|
||||||
``` yml
|
|
||||||
- name: Build and push
|
|
||||||
uses: docker/build-push-action@master
|
|
||||||
with:
|
|
||||||
...
|
|
||||||
```
|
|
||||||
|
|
|
@ -132,34 +132,3 @@ Gitea Actions目前不支持此功能。
|
||||||
|
|
||||||
不检查上下文可用性,因此您可以在更多地方使用env上下文。
|
不检查上下文可用性,因此您可以在更多地方使用env上下文。
|
||||||
请参阅[上下文可用性](https://docs.github.com/en/actions/learn-github-actions/contexts#context-availability)。
|
请参阅[上下文可用性](https://docs.github.com/en/actions/learn-github-actions/contexts#context-availability)。
|
||||||
|
|
||||||
## 已知问题
|
|
||||||
|
|
||||||
### `docker/build-push-action@v4`
|
|
||||||
|
|
||||||
请参阅[act_runner#119](https://gitea.com/gitea/act_runner/issues/119#issuecomment-738294)。
|
|
||||||
|
|
||||||
`ACTIONS_RUNTIME_TOKEN`在Gitea Actions中是一个随机字符串,而不是JWT。
|
|
||||||
但是`DOCKER/BUILD-PUSH-ACTION@V4尝试将令牌解析为JWT,并且不处理错误,因此Job失败。
|
|
||||||
|
|
||||||
有两种解决方法:
|
|
||||||
|
|
||||||
手动将`ACTIONS_RUNTIME_TOKEN`设置为空字符串,例如:
|
|
||||||
|
|
||||||
``` yml
|
|
||||||
- name: Build and push
|
|
||||||
uses: docker/build-push-action@v4
|
|
||||||
env:
|
|
||||||
ACTIONS_RUNTIME_TOKEN: ''
|
|
||||||
with:
|
|
||||||
...
|
|
||||||
```
|
|
||||||
|
|
||||||
该问题已在较新的[提交](https://gitea.com/docker/build-push-action/commit/d8823bfaed2a82c6f5d4799a2f8e86173c461aba?style=split&whitespace=show-all#diff-1af9a5bdf96ddff3a2f3427ed520b7005e9564ad)中修复,但尚未发布。因此,您可以通过指定分支名称来使用最新版本,例如:
|
|
||||||
|
|
||||||
``` yml
|
|
||||||
- name: Build and push
|
|
||||||
uses: docker/build-push-action@master
|
|
||||||
with:
|
|
||||||
...
|
|
||||||
```
|
|
||||||
|
|
Loading…
Reference in a new issue