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
I try to setup the container on a Fedora 39 host using Portainer.
My compose config:
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
So it seems like it is in a restart loop.
journalctl -b | grep cups is showing 3 messages per PID like this:
Do you have an idea how I could get it to work?