Issue Summary: Compatibility Regression between OpenList (v4.1.1+) and Claw Cloud Run
Problem Overview
The latest versions of OpenList (v4.1.1 and above) have introduced breaking changes to user permission handling that are incompatible with the security policies of Claw Cloud Run, leading to a total service outage.
Technical Breakdown
OpenList Changes: Support for PUID/PGID environment variables has been removed. The container now strictly runs as a hardcoded non-root user (UID 1001).
Claw Cloud Run Constraints: The platform enforces a security policy that prohibits chmod and chown operations. Containers are restricted from modifying file permissions on mounted volumes.
The Conflict: Upon startup, OpenList v4.1.1+ attempts to execute chmod 777 /opt/openlist/data to ensure write access. Claw Cloud Run blocks this operation.
Impact
Status: The application enters an infinite CrashLoopBackOff.
Error Log: chmod: /opt/openlist/data: Operation not permitted
Availability: The application is completely inaccessible to users.
Root Cause Analysis
Security Hardening: OpenList v4.1.1+ forces UID 1001 to improve security posture.
Permission Initialization: The entrypoint script tries to recursively change permissions on the data directory at runtime.
Policy Violation: Claw Cloud Run’s security layer intercepts and denies the chmod command, causing the application process to terminate immediately.
Requested Solution
A fix or workaround is required to allow OpenList to bypass the chmod initialization step if the directory is already writable, or a configuration option to disable mandatory permission changes during the boot sequence.
Would you like me to draft a formal GitHub Issue or a technical email to the Claw Cloud support team based on this summary?