Skip to content

test.yml: run on self-hosted [6.1.x]#214

Closed
mauritsvanrees wants to merge 3 commits into
6.1.xfrom
maurits-61x-debug-failure
Closed

test.yml: run on self-hosted [6.1.x]#214
mauritsvanrees wants to merge 3 commits into
6.1.xfrom
maurits-61x-debug-failure

Conversation

@mauritsvanrees

Copy link
Copy Markdown
Member

Currently, test.yml works, see this run from PR #421, which upgrades to Plone 6.1.5.

But then the release of 6.1.5 (via image-release.yml) fails, see this run.

Big difference: the release runs on self-hosted.

Let's first see if test.yml also starts failing when run on self-hosted.

Then we can see if we can fix that. It goes wrong in docker/setup-buildx-action@v3:

Error response from daemon:
failed to stat parent:
stat /var/lib/containerd-stargz-grpc/snapshotter/snapshots/15190/fs:
no such file or directory

There are lots of differences between self-hosted and the standard ubuntu, some older, some newer. An obvious thing to try it just to move to latest docker/setup-buildx-action@v4. But that is for later.

BTW, 6.2.1 has the same problem. But let's try on one branch for now.

@mauritsvanrees

Copy link
Copy Markdown
Member Author

@fredvd It keeps failing with the same error when using the latest docker/setup-docker-buildx action:

failed to stat parent:
stat /var/lib/containerd-stargz-grpc/snapshotter/snapshots/15190/fs: no such file or directory

I wonder if the self-hosted needs some updates.

I half remember you mentioning that maybe the self-hosted runner would no longer be needed. Am I remembering correctly?

@fredvd

fredvd commented Jul 1, 2026

Copy link
Copy Markdown
Member

Did you see my other PR where I update to the setup qemu v4 recipe. Because that's were the 6.1.5 release was hanging AFAICS #215

@mauritsvanrees

Copy link
Copy Markdown
Member Author

@fredvd For 6.1.5, docker/setup-qemu-action@v3 was fine. It is docker/setup-buildx-action@v3 (or v4) which is breaking:

https://github.com/plone/plone-backend/actions/runs/28202583156/job/83626409945

There may be some randomness involved.

Currently, `test.yml` works, see [this run](https://github.com/plone/plone-backend/actions/runs/28202581450) from PR #421, which upgrades to Plone 6.1.5.

But then the release of 6.1.5 (via `image-release.yml`) fails, see [this run](https://github.com/plone/plone-backend/actions/runs/28202583156/job/83626409863).

Big difference: the release runs on `self-hosted`.

Let's first see if `test.yml` also starts failing when run on `self-hosted`.

Then we can see if we can fix that.  It goes wrong in `docker/setup-buildx-action@v3`:

```
Error response from daemon:
failed to stat parent:
stat /var/lib/containerd-stargz-grpc/snapshotter/snapshots/15190/fs:
no such file or directory
```

There are lots of differences between self-hosted and the standard ubuntu, some older, some newer.
An obvious thing to try it just to move to latest `docker/setup-buildx-action@v4`.
But that is for later.
As expected, `test.yml` [fails](https://github.com/plone/plone-backend/actions/runs/28404941277/job/84165176967?pr=214#step:6:198) now that is is run on `self-hosted`.  So we try the first fix: use the latest version of the setup-buildx-action.
@mauritsvanrees

Copy link
Copy Markdown
Member Author

@fredvd I have rebased on 6.1.x to get your version changes, and I have updated the versions in the other files, but the test run still fails, now with:

Run docker/setup-buildx-action@v4
...
Error:
ERROR:
Error response from daemon:
apply layer error for "":
failed to prepare extraction snapshot "extract-881329676--v_P
sha256:05373ad2322b7d605314c8f8f192ae0058723e6f1fa3293c14affc27d383288b":
NotFound: failed to create snapshot:
missing parent "moby/21065/sha256:a8d26d037006414043b277ecb95287692d0960219289d9e27b0bcea0ce233b02"
bucket: not found

@mauritsvanrees

Copy link
Copy Markdown
Member Author

plone-backend 6.1.5 is available now, using Fred's changes on the 6.1.x branch. And 6.2.1 as well. Thanks!
So let's close this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants