Skip to content

Latest path changes on 3.10-slim image leading to errors when building applications with staticx #786

Closed
@oktavlachs

Description

@oktavlachs

Hi everyone and thank you for maintaining this project. I have used your docker images heavily over the past years :)

Since this morning I am facing issues when running staticx against one of my Python applications. I have successfully built an image yesterday and have not changed anything in my application, but with the latest 3.10-slim image, I get an error with unsupported RPATH/RUNPATH tags, I believe because of the way the paths in the image have changed to absolute paths.
#785

I know this sounds like a very specific issue outside your scope, but I would like to at least know if this is intended on your side or not.
Please find the link to the issue with staticx here:
JonathonReinhart/staticx#188

Example:

...
/tmp/staticx-pyi-1eb5z08n/lib-dynload/_asyncio.cpython-310-x86_64-linux-gnu.so: DT_RUNPATH='/../lib:$ORIGIN/../lib'
...

Would be great to get a quick comment on this.

Cheers!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions