Describe the bug
Running in Docker on a Raspberry Pi 5 (Ubuntu 24.10)
After updating with tag sourceforge-stable-pulse today I get this error in logs and the container does not start:
/app/bin/squeezelite-pulseaudio: error while loading shared libraries: libpulse.so.0: cannot open shared object file: No such file or directory
To Reproduce
Start the docker container using the docker-compose.yml on an arm64 system
Expected behavior
The container should start normally without error
Docker run command
n/a I am using docker-compose
Docker-compose.yaml file
squeezeamppi:
image: giof71/squeezelite:sourceforge-stable-pulse
container_name: squeezeampi
devices:
- /dev/snd:/dev/snd
environment:
- SQUEEZELITE_MODE=PULSE
- SQUEEZELITE_NAME=squeezeamppi
- SQUEEZELITE_LOG_CATEGORY_ALL=debug
- SQUEEZELITE_SERVER_PORT=192.168.x.x
volumes:
- /home/neil/containers/squeezeampi/config:/config
- /run/user/1000/pulse:/run/user/1000/pulse
#entrypoint:
# - /bin/bash
# - -c
# - apt update && apt install -y libpulse0 && /app/bin/run-squeezelite.sh
Screenshots
n/a
Operating system(please complete the following information):
- OS: Ubuntu 24.10
- Architecture: arm64
- Version: latest sourceforge-stable-pulse
Additional context
If I override the entrypoint to manually install/update libpulse0 the container starts normally (uncomment in docker-compose.yml)
There are no outstanding packages/updates to install on the host OS
I haven't done any more testing beyond updating the container running on the Raspberry Pi 5
I have another Raspberry Pi 5 running Raspbian Bookworm and it has the same problem
Describe the bug
Running in Docker on a Raspberry Pi 5 (Ubuntu 24.10)
After updating with tag
sourceforge-stable-pulsetoday I get this error in logs and the container does not start:/app/bin/squeezelite-pulseaudio: error while loading shared libraries: libpulse.so.0: cannot open shared object file: No such file or directoryTo Reproduce
Start the docker container using the docker-compose.yml on an arm64 system
Expected behavior
The container should start normally without error
Docker run command
n/a I am using docker-compose
Docker-compose.yaml file
Screenshots
n/a
Operating system(please complete the following information):
Additional context
If I override the entrypoint to manually install/update libpulse0 the container starts normally (uncomment in docker-compose.yml)
There are no outstanding packages/updates to install on the host OS
I haven't done any more testing beyond updating the container running on the Raspberry Pi 5
I have another Raspberry Pi 5 running Raspbian Bookworm and it has the same problem