Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error setting rlimits for ready process: error setting rlimit type 8: operation not permitted: unknown

sapentiae commented 1 year ago

m1ntyduck commented 1 year ago

Same issue on Proxmox 7.4-15 using a stndard Ubuntu LXC (22.04)

Wazuh Manager - starts fine

Wazuh Indexer; returns the message:-

Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error setting rlimits for ready process: error setting rlimit type 8: operation not permitted: unknown

Ben-Higham commented 1 year ago

Same issue on Proxmox 7.4-15 using a stndard Ubuntu LXC (22.04)

Wazuh Manager - starts fine

Wazuh Indexer; returns the message:-

Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error setting rlimits for ready process: error setting rlimit type 8: operation not permitted: unknown

Same for me, also in Proxmox 7.4-15 but in Debian 11 standard container.

Nonesence999 commented 1 year ago

Sam issue using Docker on windows whit debian dev env

Ben-Higham commented 1 year ago

I found someone getting the same error with Elasticsearch in another docker compose file and their solution worked for me.

In docker-compose.yml comment out the following lines then try compose up:

   # ulimits:
   #   memlock:
   #     soft: -1
   #     hard: -1
   #   nofile:
   #     soft: 65536
   #     hard: 65536

m1ntyduck commented 1 year ago

Thanks @Ben-Higham this worked for me.

p1r4t3-s4il0r commented 11 months ago

Hello, I know this issue is a bit old but I'm facing the same issue using docker rootless. Have anyone manage to get trough this ? Thanks

camorobot commented 6 months ago

Are there any updates? having trouble with the same error.

ozoumi commented 5 months ago

I found someone getting the same error with Elasticsearch in another docker compose file and their solution worked for me.

In docker-compose.yml comment out the following lines then try compose up:
   # ulimits:
   #   memlock:
   #     soft: -1
   #     hard: -1
   #   nofile:
   #     soft: 65536
   #     hard: 65536

thanks, it worked

lpaxton-bigwx commented 3 months ago

I found someone getting the same error with Elasticsearch in another docker compose file and their solution worked for me.

In docker-compose.yml comment out the following lines then try compose up:
   # ulimits:
   #   memlock:
   #     soft: -1
   #     hard: -1
   #   nofile:
   #     soft: 65536
   #     hard: 65536

Worked for me on Proxmox 8.2.4 using single node

jov-one commented 2 months ago

I had the same problem with Elasticsearch running in LXC on Proxmox and I don't suggest commenting out ulimits for Elasticsearch in docker-compose

If you are encountering issues related to memory locking limits (memlock) when running Elasticsearch (or other memory-intensive applications) inside LXC containers on Proxmox, you can resolve this by setting the memlock limit to unlimited for that LXC. This ensures that your application can lock the required amount of memory and avoid performance issues related to swapping.

To fix this, edit the LXC config file by adding lxc.prlimit.memlock=-1 and reboot the container.

rallisf1 commented 1 month ago

To fix this, edit the LXC config file by adding lxc.prlimit.memlock=-1 and reboot the container.

Also add lxc.prlimit.nofile:655360

wazuh / wazuh-docker