You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When I try to pull the latest image of activepieces via docker image pull activepieces/activepieces:latest on my rootless docker-server I get the following error:
failed to register layer: failed to Lchown "/usr/src/app/dist/packages/server/api/node_modules/buffer-equal-constant-time/.npmignore" for UID 718322462, GID 454177323 (try increasing the number of subordinate IDs in /etc/subuid and /etc/subgid): lchown /usr/src/app/dist/packages/server/api/node_modules/buffer-equal-constant-time/.npmignore: invalid argument
The error in turn blocks an installation via portainer aswell (portainer thinks that there is no image activepieces/activepieces:latest). Some research showed that this seems to be a problem within the image (see moby/moby#45757 ) and not with docker in general. The image works fine on my rootfull-dockerserver.
Please fix. :)
Additional context
There is no good reason that activepieces should need a root-full docker-instance to work.
Edit: The referenced link seem to have it fixed. See m9sweeper/m9sweeper#117 and subsequent links.
The text was updated successfully, but these errors were encountered:
Husky110
changed the title
[BUG]: Installation on rootless-docker instance failes
[BUG]: Installation on rootless-docker instance fails
Jun 8, 2024
I am not sure currently which package is causing that, this going need sometime to find, If anyone reading this and find why it's happening please let us know.
Describe the bug
When I try to pull the latest image of activepieces via
docker image pull activepieces/activepieces:latest
on my rootless docker-server I get the following error:The error in turn blocks an installation via portainer aswell (portainer thinks that there is no image activepieces/activepieces:latest). Some research showed that this seems to be a problem within the image (see moby/moby#45757 ) and not with docker in general. The image works fine on my rootfull-dockerserver.
Please fix. :)
To Reproduce
Steps to reproduce the behavior:
docker image pull activepieces/activepieces:latest
Expected behavior
The image should pull normally.
Additional context
There is no good reason that activepieces should need a root-full docker-instance to work.
Edit: The referenced link seem to have it fixed. See m9sweeper/m9sweeper#117 and subsequent links.
The text was updated successfully, but these errors were encountered: