Image not being pushed with v1
See original GitHub issueHey there,
I’m using v1 with the following configuration to build and publish the image:
publish_docker:
runs-on: [self-hosted, tsa, myrunner]
if: github.event.action == 'closed' && github.event.pull_request.merged && !needs.release.outputs.skip
needs: release
steps:
- name: Check out the repo
uses: actions/checkout@v2
- name: Push to Docker Registry
uses: docker/build-push-action@v1
with:
username: ${{ secrets.DOCKER_USER }}
password: ${{ secrets.DOCKER_PASSWORD }}
registry: docker-local.registry.company.com
repository: name/app
build-args: GITHUB_USER=${{ secrets.GITHUB_USER }},GITHUB_TOKEN=${{ secrets.GITHUB_TOKEN }}
tag_with_ref: true
When the action is ran, it seems that it builds the image correctly but it’s not pushing that to the repo, it finishes with the message:
Pushing image []
And when I check the repo, I see that it was not actually pushed.
Do you know why it ends like this? I mean it ends without giving any error, just that message and it doesn’t do the push process
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Can not push Image to DockerHub - Docker Community Forums
Hi. I am not able to push image to my repository in DockerHub. First I try done this without creating in the DockerHub...
Read more >docker: push image not work - Stack Overflow
When I push or pull in server-2, docker-registry logs 404 records: 192.168.1.152 - - [14/Aug/2015:12:34:41 +0000] "GET /v1/_ping HTTP/1.1" ...
Read more >Getting 404 (image not found) when trying /v1/ ... - GitHub
My docker pul call to /v1/repositories/mycompany/myname/images was returning an entry with an id which did not exist in the registry (not in the...
Read more >Pushing and pulling images | Container Registry documentation
This document focuses on pushing and pulling images with Docker. Note: Starting with GKE node version 1.19, the default node image for Linux...
Read more >Pulling and Pushing Images in the Docker Client - Harbor docs
In your Docker client is not configured for insecure registries, you will see the following error when you attempt to pull or push...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Finally I made it work by adding the tags input. And yeah, I’m considering to migrate to v2. Thanks
It might be an event that is not handled to generate tags. Can’t really tell without the complete workflow.
Anyway, I suggest to migrate to
docker/build-push-action@v2
as v1 is deprecated. To handle tags and labels with v2 see https://github.com/docker/build-push-action/blob/master/docs/advanced/tags-labels.md.