I study Github Actions + Github Package Registry.
I have an error when i'm trying to push image to Github Package Registry by Actions
Login Succeeded The push refers to repository [docker.pkg.github.com/marley-nodejs/mern-stack-front-to-back-v2.0/client.anketa.info] 412bcb172467: Preparing 5d7983547f5b: Preparing ce3539cc1849: Preparing 16d1b1dd2a23: Preparing 2db44bce66cd: Preparing unknown blob ##[error]Process completed with exit code 1.
Here is link on error:
Project is opensource, you can check everything.
What is wrong?
If i made this topic in not right place, please move it.
Solved! Solved! Go to Solution.
I tried example by Chris Patterson.
And this example works for me.
But i still did not solve problem with my project.
I have also met this issue. But after I run the task again, everything works fine. Seems it's a random issue.
I think it might be an issue with Package Registry. I'm seeing the same thing. I reported to GitHub Support, and they seemed to confirm an issue on their end escalated to engineering.
It looks like I am getting some new assets on my package page every time I try to push, but the only version that shows is "docker-base-layer" when I should see tags for "latest" and "[MyBuildId]". https://github.com/collinbarrett/FilterLists/packages/26496
Build Def: https://github.com/collinbarrett/FilterLists/blob/1ed56d3bf3e75e1a6e80993f370a8126067afe3a/azure-pip...
Build Results: https://dev.azure.com/collinbarrett/FilterLists/_build/results?buildId=1561
I have exactly the same issue with Github Package Repository than @collinbarrett while pushing, only "docker-base-layer" is updated! So it seems that this issue is still not fixed
Today i received an email "Announcing general availability for GitHub Actions and GitHub Package Registry".
Clicked here https://github.com/features/package-registry
On "SignUp for Free Beta"
And tried run with my configs from post 1.
Looks everything works.
Yeah @marley-nodejs the workflows runs! But, if you get back from the Github Package Registry your just built docker image with the tag latest, which is the one you use to build, do you get the last change? I don't, it seems that it is the tag docker-base-layer which gets the changes
Forget my last message! It seems that it is working now, at least when I get back the latest image on my local machine, the image got my latest code change. So, it seems that it is my CD action which doesn't work
Hi @laurentkempe l
I made another one question about GPR.
Possible you know solution.
If know please answear.