fix(docker): Resolve liburing.so.2 loading error for non-root users #987
No reviewers
Labels
No labels
Bug
Cherry-picking
Database
Dependencies
Dependencies/Renovate
Difficulty
Easy
Difficulty
Hard
Difficulty
Medium
Documentation
Enhancement
Good first issue
Help wanted
Inherited
Matrix/Administration
Matrix/Appservices
Matrix/Auth
Matrix/Client
Matrix/Core
Matrix/Federation
Matrix/Hydra
Matrix/MSC
Matrix/Media
Meta
Meta/CI
Meta/Packaging
Priority
Blocking
Priority
High
Priority
Low
Security
Status/Blocked
Status
Confirmed
Status
Duplicate
Status
Invalid
Status
Needs Investigation
To-Merge
Wont fix
old/ci/cd
old/rust
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
continuwuation/continuwuity!987
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "tom/fix-liburing"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Container failed to start when running as non-root (user 1000:1000) because copied directories had restrictive 770 permissions, likely due to different umask in persistent BuildKit. Non-root users couldn't access /usr/lib to load required dynamic libraries.
Adds
--chmod=755to all COPY commands to explicitly set permissions and improves library extraction with robust lddtree processing. Also fixes workflow syntax error and removesdocker/**from paths-ignore to ensure Docker changes trigger CI builds.d7e4348234a9c1d165d7fix(docker): Include liburing runtime library for io_uring supportto fix(docker): Resolve liburing.so.2 loading error for non-root usersa9c1d165d7d92da9d8e6d92da9d8e67b3055be377b3055be370d9a9aa3880d9a9aa3884dd1cbc8034dd1cbc803fff9629b0fIt was fun resolving this permission issue...
COPY --chmodin Docker apparently only modifies the files, not the directories, so I've added a littleprepperstage between thebuilderand the scratch output so it can organise the files into "layers" and set the mode correctly before copying the layers into the final scratch for export.I can confirm this has resolved the permissions issue for me, either way!