Skip to content

Conversation

dirkmueller
Copy link
Member

No description provided.

@dcermak
Copy link
Contributor

dcermak commented Jul 16, 2024

This fails only with podman (and not with docker) with:

----------------------------- Captured stderr call -----------------------------
/usr/bin/tar: pcre-8.45/cmake: Cannot change mode to rwxr-xr-x: Operation not permitted
/usr/bin/tar: pcre-8.45/m4: Cannot change mode to rwxr-xr-x: Operation not permitted
/usr/bin/tar: pcre-8.45/sljit: Cannot change mode to rwxr-xr-x: Operation not permitted
/usr/bin/tar: pcre-8.45/testdata: Cannot change mode to rwxr-xr-x: Operation not permitted
/usr/bin/tar: pcre-8.45/doc/html: Cannot change mode to rwxr-xr-x: Operation not permitted
/usr/bin/tar: pcre-8.45/doc: Cannot change mode to rwxr-xr-x: Operation not permitted
/usr/bin/tar: pcre-8.45: Cannot change mode to rwxr-xr-x: Operation not permitted
/usr/bin/tar: Exiting with failure status due to previous errors
==> Error: ProcessError: Command exited with status 2:
    '/usr/bin/tar' '-oxf' '/tmp/root/spack-stage/spack-stage-pcre-8.45-skm3fvdkmhaayc5hgrucm4okz24qkbry/pcre-8.45.tar.bz2'
==> Warning: Skipping build of zsh-5.8-ldow7yzmcdkp2egkncjpfbqxzbjl2low since pcre-8.45-skm3fvdkmhaayc5hgrucm4okz24qkbry failed
==> Error: Terminating after first install failure: ProcessError: Command exited with status 2:
    '/usr/bin/tar' '-oxf' '/tmp/root/spack-stage/spack-stage-pcre-8.45-skm3fvdkmhaayc5hgrucm4okz24qkbry/pcre-8.45.tar.bz2'
error building at STEP "RUN cd /opt/spack-environment && spack env activate . && spack install --fail-fast && spack gc -y": error while running runtime: exit status 1

Iirc you already fixed a comparable issue in the past Dirk, do you recall what the fix was?

@dirkmueller
Copy link
Member Author

This fails only with podman (and not with docker) with:

Iirc you already fixed a comparable issue in the past Dirk, do you recall what the fix was?

we don't have a fix. the problem is that tumbleweed uses some syscalls that are blocked on the workers and fails. the workaround was to add --no-same-permissions --no-same-owner

@dirkmueller dirkmueller marked this pull request as draft July 17, 2024 14:40
@dirkmueller
Copy link
Member Author

(this will need more work)

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