Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Container getting "kernel: __vm_enough_memory: pid: xxxx, comm: cupsd, not enough memory for the allocation" #105

Open
dma7 opened this issue Apr 20, 2024 · 1 comment

Comments

@dma7
Copy link

dma7 commented Apr 20, 2024

I try to setup the container on a Fedora 39 host using Portainer.

My compose config:

version: '3.3'
services:
    cupsd:
        image: olbat/cupsd
        container_name: cupsd
        volumes:
            - '/var/run/dbus:/var/run/dbus'
            - '/dev/bus/usb:/dev/bus/usb'
        ports:
            - '631:631'
        privileged: true
        restart: always

When I deploy the stack, Portainer is telling me that it was successful. But when I look into "Containers" section, I see that the container has no port bound which indicates an issue.

docker container ls output is like this

CONTAINER ID   IMAGE                           COMMAND                CREATED          STATUS                          PORTS                                                                                            NAMES
bdd39df5e0d5   olbat/cupsd                     "/usr/sbin/cupsd -f"   11 minutes ago   Restarting (1) 25 seconds ago              

So it seems like it is in a restart loop.

journalctl -b | grep cups is showing 3 messages per PID like this:

Apr 20 18:16:37 xxxx.dip0.t-ipconnect.de kernel: __vm_enough_memory: pid: 7902, comm: cupsd, not enough memory for the allocation
Apr 20 18:16:37 xxxx.dip0.t-ipconnect.de kernel: __vm_enough_memory: pid: 7902, comm: cupsd, not enough memory for the allocation
Apr 20 18:16:37 xxxx.dip0.t-ipconnect.de kernel: __vm_enough_memory: pid: 7902, comm: cupsd, not enough memory for the allocation


Do you have an idea how I could get it to work?

@dma7
Copy link
Author

dma7 commented Apr 20, 2024

Ok, I managed to help myself.

The problem is described here.

Starting the container with the additional parameter --ulimit nofile=1024:1024 will do the trick

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant