actions/docker-build-push
actions/docker-build-push
3
0
Fork 0
mirror of https://gitea.com/docker/build-push-action.git synced 2024-11-27 11:59:37 +01:00
Code Issues Projects Activity Pipelines

Merge pull request #1266 from crazy-max/update-trbsht

Browse source 
update troubleshooting markdown
This commit is contained in:
CrazyMax 2024-11-26 10:14:48 +01:00 committed by GitHub
commit 22cd91d73b
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 0 additions and 27 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

27
TROUBLESHOOTING.md
View file

@ -4,7 +4,6 @@
* [BuildKit container logs](#buildkit-container-logs)
* [With containerd](#with-containerd)
* [`repository name must be lowercase`](#repository-name-must-be-lowercase)
* [Image not loaded](#image-not-loaded)
## Cannot push to a registry
@ -136,29 +135,3 @@ Or a dedicated step to sanitize the slug:
push: true
tags: ${{ steps.repo_slug.outputs.result }}:latest
```
## Image not loaded
Sometimes when your workflows are heavy consumers of disk storage, it can happen that build-push-action declares that the built image is loaded, but then not found in the following workflow steps.
- You can use the following solution as workaround, to free space on disk before building docker image using the following workflow step
```yaml
# Free disk space
- name: Free Disk space
shell: bash
run: |
sudo rm -rf /usr/local/lib/android # will release about 10 GB if you don't need Android
sudo rm -rf /usr/share/dotnet # will release about 20GB if you don't need .NET
```
- Another workaround can be to call `docker/setup-buildx-action` with docker driver
```yaml
name: Set up Docker Buildx
uses: docker/setup-buildx-action@v3
with:
driver: docker
```
More details in the [related issue](https://github.com/docker/build-push-action/issues/321)