Closed danbo closed 10 months ago
Hey, thanks for the report. So it only happens for libass, other tar extractions are ok? maybe uses saner ids? did some googling and seems others have run into similar issues with rootless container etc that uses uid/gid mappings, is that the case for you too?
Anyways #367 should fix the issue i think
I was able to confirm by running the following command on a few dependencies:
tar -tvf <file.tar.gz>
libass was the only one that listed a non-root uid/gid, ie
tar -tvf libass-0.17.1.tar.gz
drwxr-xr-x 197609/197609 0 2023-02-26 11:05 libass-0.17.1/
...
tar -tvf v2.3.1.tar.gz
drwxrwxr-x root/root 0 2022-04-11 13:06 vmaf-2.3.1/
...
tar -tvf v1.0.3.tar.gz
drwxrwxr-x root/root 0 2014-08-18 11:29 aribb24-1.0.3/
...
I got it to work by adding the
--no-same-owner
option to the tar command here:tar xf libass.tar.gz ---no-same-owner && \
Docker version 24.0.7, build afdd53b