Failed to pull manifest by the resolved digest #53
Comments
|
Hello, thank you for your message. I have just hit this myself and have found out what the issue is: recently Github bumped the default OS from Ubuntu 18.04 to Ubuntu 20.04. I'm not sure why this has caused an issue, but it's certainly too much of a coincidence to ignore. My plan is to hardcode the reference to the previously working Ubuntu 18.04, make a patch to the v5 release, then move on to investigate what incompatibility there is caused by the newer OS. |
|
Ah, great. Thank you very much! So I can stay at |
|
I definitely want this to continue working on any ubuntu (and I'm also planning how to make it work on Windows, but that's another story). Currently not sure exactly what's failing, but I hope I'll find it soon as it's going to start affecting a lot of people, including my own repositories. Any help identifying the issue is appreciated. |
|
I am getting the same here on my repos 😬 I tried downgrading from ubuntu-20.04 (which I was on before, which worked) to 18.04. Did not help. |
Seems to be to do with the docker version as opposed to Ubuntu (obviously newer ubuntu shipped with newer Docker) https://docs.docker.com/engine/deprecated/#pulling-images-from-non-compliant-image-registries Attempting to help look at what might be the exact cause and will report back if i find anything. Anyone seeing this on any other GH registry hosted images or just this one? |
|
Could be a docker thing. Lately I'm getting errors like |
|
I can also confirm what @polesen states: downgrading Ubuntu does not fix this. I'm testing on https://github.com/php-actions/example-composer - investigating Docker repository now. |
|
I hope it not that the newish Docker API rate limiting is affecting the GitHub Action servers. |
|
Maybe it is time to switch away from docker.pkg.github.com in the php-actions build script that is sourced, as it seems like that registry does not conform to the (docker)spec and will be a problem also going forward: GCHR seems to be their(github's) solution for docker images, going forward: Which should be a compliant registry. |
|
This repo originally used GHCR but it required the user to register their own Personal Access Token to use, and plenty of other limitations that made it run incredibly slowly and tediously. It might be improved now, but it was almost unusable before. I'll look into it again once I've resolved this. |
|
Hey everyone, please can you all test to see if a change I've made fixes this for your repositories? If you could change I've checked and there have been loads of updates to GHCR. Mainly, the GITHUB_TOKEN environment variable now works, which is great - let's see if this simple fix will resolve our issues. |
|
@g105b thx for investigating this issue!! On my project with |
|
Phew! I'll wait for confirmation from others, then I'll make a patch release to |
|
It works, and it does not work. It seems to be getting the image now, but the previous bug from this issue #47 re-appears, not being able to clone private repos, which I guess is due to this fix branch being branched from master. So, a backport of the ghcr fix to v5 would probably work for me 👍 |
|
Initially I got the following error Having followed those instructions to enable improved container support, it does indeed work as expected using |
|
I've taken into account @polesen's latest tip, and have updated the |
|
Update: I've tested all the various setups that I've come across while maintaining this repo here: https://github.com/php-actions/example-composer/actions The latest run "Update all workflows to test April 2021 issue fix" changed all workflow config files to use If there's any other case that anybody can report that doesn't work, I'll try and replicate in the example repository before making a backport patch into v5. I'll make the patch at 09:00AM BST tomorrow (Wednesday 7th April) if there aren't any more issues reported on this. |
|
My block - name: Install dependencies
uses: php-actions/composer@april-2021-issue
with:
php_version: 7.4
version: 2...runs through when using But my block: - name: Run tests
uses: php-actions/composer@april-2021-issue
with:
command: run test
php_version: 7.4
version: 2... fails in https://github.com/qownnotes/api/runs/2280392933?check_suite_focus=true#step:4:253. |
|
@g105b Excellent, my build runs without errors now on |
|
On my project, it started to work with v5 (without any changes). - name: Install composer dependencies
uses: php-actions/composer@v5
with:
php_version: 7.4
version: 2 |
|
Initially, I got the same error as @benswinburne:
After enabling improved container support, it started to work with v5 on |
|
It looks like the issue is due to something changing with the GitHub container repository. I'll contact their support to learn more before making any changes to the v5 patch, as I want to ensure any changes are actually going to improve things. |
|
I'm waiting to hear back from Github Support, but in the meantime I have successfully managed to run this action without having to change anything, so it seems the issue was only temporary. Please can people provide an update here if they're still having any issues? |
|
I've been running other workflows today, which run with |
|
I also can confirm |
|
Please feel free to re-open this issue if there are any other problems using the container repository. |
|
Hi everyone. I'm just following up with the response from GitHub support.
|
|
Apparently i am still getting the same error, i already enabled the improved container support. |
|
This issue popped up for me just now as well. |
|
Also experiencing this "/usr/local/bin/composer: line 2: syntax error: unexpected newline" as of this morning. |
|
I'll jump back onto the ticket for Github support. I don't know where we can find out any more information because https://www.githubstatus.com/ tells us "All systems are operational"... |
|
Is there any update to this issue? We're experiencing it as well in v6 |
Thank you for this nice GitHub action! It worked great until recently when I use:
(See https://github.com/qownnotes/api/blob/4a313056a824ba928eaedf6f8e483a88d1ae363e/.github/workflows/test.yml#L17-L21)
I get:
(See https://github.com/qownnotes/api/runs/2278527522?check_suite_focus=true)
Retrying the build process doesn't help.
Did anyone else see this?
The text was updated successfully, but these errors were encountered: