Compose container cannot start due to restricted memory lock limits
Error recorded 1 times in PanelAlpha Engine deploys on Docker Compose. The deploy log below is the recorded failure output.
TypeErrorAn error that occurred in the deployed application. It is not necessarily a PanelAlpha Engine error, but we keep working on improvements so you run into fewer of them.
Seen1 times
WhereDocker Compose
StatusObservedOur team will look into this soon, verify the cause and try to fix it in an upcoming release.
Why it happens
The Docker daemon created the volumes, network, and containers, but the nested runtime could not start Elasticsearch. The hardened Compose settings attempted to apply a memory-lock limit (rlimit type 8), which the host or DinD runtime does not permit.
What the log looks like
Deploy log
Starting application (docker compose up -d)Container archivist-es StartingError response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: error during container init: error setting rlimits for ready process: error setting rlimit type 8: operation not permitted