v3.13/main/samba-4.13.8-r0: smb segfaults upon client connection attempt
I'm experiencing a segfault issue with the Samba package in Alpine 3.13 that doesn't occur for me in Alpine 3.12.
I have attached the exact Docker setup that results in the issue I'm seeing.
To reproduce it, you'll have to edit the volume path that maps to
/samba/public in the
docker-compose.yml file. Then run docker-compose up. After the container boots up, try to connect to the samba server using a guest account. I have included the log that I see in the
docker-compose_up.log in the zip file, and the core dump at
I'm running this on a Raspberry Pi 4, so I'm using the linux/arm/v7 image. I don't know if this applies to all the Samba packages or just the armv7 build. I don't have an x86_64 machine handy at the moment to test with. I tried on a MBP with Docker Desktop for Mac, but that makes networking complicated with Samba and I wasn't able to fully test the issue since it requires a client to attempt to connect to the Samba server.
The client I'm trying to use to connect to the samba server is the default MacOS Finder client. If you only change the Dockerfile to use Alpine 3.12 instead of 3.13, this exact setup works flawlessly. (I haven't been able to test against the edge builds yet as I'm using
supervisord to manage the two Samba processes in the Docker image and the Supervisor package currently has issues in edge.