Repository navigation
PHP-FPM issue in Docker Desktop 4.27.2: WARNING: [pool www] child 85 exited on signal 11 (SIGSEGV) #7182
Copy link
Copy link
Closed
Description
Description
After updating to Docker Desktop 4.27.2 from 4.26.1 PHP-FPM containers cannot run without crashing with the error:
2024-02-09 10:17:13 pimcore-fpm-1 | 172.19.0.6 - 09/Feb/2024:10:17:13 +0100 "GET /index.php" 200
2024-02-09 10:17:14 pimcore-fpm-1 | [09-Feb-2024 10:17:14] WARNING: [pool www] child 85 exited on signal 11 (SIGSEGV) after 239.493217 seconds from start
Reproduce
- Build a PHP-based image with a Composer package and put it behind an Nginx proxy.
- Run it using
docker compose up -d
Expected behavior
It should run as well as it did in 4.26.1
docker version
Client:
Cloud integration: v1.0.35+desktop.10
Version: 25.0.3
API version: 1.44
Go version: go1.21.6
Git commit: 4debf41
Built: Tue Feb 6 21:13:26 2024
OS/Arch: darwin/arm64
Context: desktop-linux
Server: Docker Desktop 4.27.2 (137060)
Engine:
Version: 25.0.3
API version: 1.44 (minimum version 1.24)
Go version: go1.21.6
Git commit: f417435e5f6216828dec57958c490c4f8bae4f98
Built: Wed Feb 7 00:39:16 2024
OS/Arch: linux/arm64
Experimental: false
containerd:
Version: 1.6.28
GitCommit: ae07eda36dd25f8a1b98dfbf587313b99c0190bb
runc:
Version: 1.1.12
GitCommit: v1.1.12-0-g51d5e94
docker-init:
Version: 0.19.0
GitCommit: de40ad0
### docker info
```bash
Client:
Version: 25.0.3
Context: desktop-linux
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.12.1-desktop.4
Path: /Users/nikbr/.docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v2.24.5-desktop.1
Path: /Users/nikbr/.docker/cli-plugins/docker-compose
debug: Get a shell into any image or container. (Docker Inc.)
Version: 0.0.24
Path: /Users/nikbr/.docker/cli-plugins/docker-debug
dev: Docker Dev Environments (Docker Inc.)
Version: v0.1.0
Path: /Users/nikbr/.docker/cli-plugins/docker-dev
extension: Manages Docker extensions (Docker Inc.)
Version: v0.2.21
Path: /Users/nikbr/.docker/cli-plugins/docker-extension
feedback: Provide feedback, right in your terminal! (Docker Inc.)
Version: v1.0.4
Path: /Users/nikbr/.docker/cli-plugins/docker-feedback
init: Creates Docker-related starter files for your project (Docker Inc.)
Version: v1.0.0
Path: /Users/nikbr/.docker/cli-plugins/docker-init
sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
Version: 0.6.0
Path: /Users/nikbr/.docker/cli-plugins/docker-sbom
scout: Docker Scout (Docker Inc.)
Version: v1.4.1
Path: /Users/nikbr/.docker/cli-plugins/docker-scout
WARNING: Plugin "/Users/nikbr/.docker/cli-plugins/docker-scan" is not valid: failed to fetch metadata: fork/exec /Users/nikbr/.docker/cli-plugins/docker-scan: no such file or directory
Server:
Containers: 18
Running: 11
Paused: 0
Stopped: 7
Images: 36
Server Version: 25.0.3
Storage Driver: overlayfs
driver-type: io.containerd.snapshotter.v1
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 2
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 runc
Default Runtime: runc
Init Binary: docker-init
containerd version: ae07eda36dd25f8a1b98dfbf587313b99c0190bb
runc version: v1.1.12-0-g51d5e94
init version: de40ad0
Security Options:
seccomp
Profile: unconfined
cgroupns
Kernel Version: 6.6.12-linuxkit
Operating System: Docker Desktop
OSType: linux
Architecture: aarch64
CPUs: 9
Total Memory: 23.44GiB
Name: docker-desktop
ID: 8f590826-49c3-4f7b-8c5d-0d6228d1cf1a
Docker Root Dir: /var/lib/docker
Debug Mode: false
HTTP Proxy: http.docker.internal:3128
HTTPS Proxy: http.docker.internal:3128
No Proxy: hubproxy.docker.internal
Experimental: false
Insecure Registries:
hubproxy.docker.internal:5555
127.0.0.0/8
Live Restore Enabled: false
WARNING: daemon is not using the default seccomp profile
### Diagnostics ID
B99BCF91-9CAF-4D12-AE8B-A4858EC43329/20240209095720
### Additional Info
I thought this was supposed to be fixed in 4.27.2 according to the release notes?
Reacted by DelMarr
Activity
dgageot commentedon Feb 9, 2024
@NiklasBr this would really help if you could share the complete Dockerfile and compose files that you use. With it, we can probably fix your issue under an hour. Without, it will take much much longer. If you can provide those files, that would be awesome!
NiklasBr commentedon Feb 9, 2024
Nginx Dockerfile:
NiklasBr commentedon Feb 9, 2024
PHP application Dockerfile:
dgageot commentedon Feb 9, 2024
@NiklasBr do you run this with Rosetta or Qemu?
NiklasBr commentedon Feb 9, 2024
NiklasBr commentedon Feb 9, 2024
@dgageot I also tried
EXPERIMENTAL_DOCKER_DESKTOP_FORCE_QEMU=1 docker build …but it did not change anything.dgageot commentedon Feb 9, 2024
Your issue is a run issue, not a build issue. Could you try with and without Rosetta enabled?
That should at least give you different errors in both cases.
NiklasBr commentedon Feb 12, 2024
Same error without Rosetta enabled:
dgageot commentedon Feb 13, 2024
This can't be a rosetta error
NiklasBr commentedon Feb 13, 2024
Not disagreeing, but in real life it is still a blocking problem. Cannot use the Docker license I am paying for at the moment.
dgageot commentedon Feb 13, 2024
@NiklasBr That would be easier to help you with a basic project to repro. You shared dockerfiles but they rely on plenty of files on your system.
You shared Rosetta logs but they are qemu in fact.
I really really want to help you but it requires way too much guessing on my part.
NiklasBr commentedon Feb 13, 2024
I have always been willing to share screen and details in a non-public forum due to the fact that they contain customer data.
dgageot commentedon Feb 13, 2024
Can you contact me at david.gageot@docker.com to organise a call?
delmarr commentedon Feb 15, 2024
I've been following this thread and #7037
opcache seems to be failing for me in a simple setup.
Here is my setup

OS: Sonoma 14.3.1
Docker desktop version: Docker Desktop 4.27.2
Docker file
Commands
docker build -t opcache-php Dockerfiledocker run --rm -it opcache-phpThen inside the container
As you can see httpd crashes on start.
dgageot commentedon Feb 15, 2024
Thanks @delmarr, I was able to reproduce. I'll take a close look later today or tomorrow.
Here are the command I used (slightly modified):
dgageot commentedon Feb 16, 2024
@delmarr @NiklasBr for both of you, the same code fails both on qemu and rosetta. And it used to work in both cases in Docker Desktop 4.26.1. I think you are seeing a variant of the same issue.
I've got a fix for Rosetta being evaluated. Hopefully it'll make it into 4.28.0. This the continuation of the work to prevent php and friends to segfault under Rosetta when Huge Pages are enabled on the kernel.
I'm also investigating a fix for Qemu. This one is again an issue with Qemu 8.1.5 that we didn't have in 6.something. Not sure if this one will make it into 4.28.0
NiklasBr commentedon Feb 19, 2024
@dgageot I see the release notes are taking shape which mentions this issue. The pre-release build you sent me did not resolve it as you remember, is there a new one to test?
dgageot commentedon Feb 19, 2024
Hey @NiklasBr, 4.28.0 should be out very soon. I expect it to fix your issue on Rosetta. Not on Qemu, though. Qemu 8.1.5 still has a regression that is closely related to your issue but that we couldn't totally fix.
I'll ping you as soon as 4.28.0 is out.
dgageot commentedon Feb 26, 2024
@delmarr @NiklasBr Could you give a try to Docker Desktop 4.28? It should be fixed on Rosetta. On QEMU, it depends of the workflow. Some are still broken.
NiklasBr commentedon Feb 27, 2024
No more Signal 11 errors for the first few hours! 🎊
Though it introduced a new one:
Warning: include(vendor/symfony/console/Event/ConsoleErrorEvent.php): Failed to open stream: Too many open fileswhich does not happen in v4.26.1 and this error pops up all the time. I click "re-apply" and twenty minutes later it's back:dgageot commentedon Feb 27, 2024
@NiklasBr the popup is a known issue. It's fixed on our side and will ship either with a 4.28.1 or with 4.29.
The
too many files error, I don't have enough information to guess where it comes from.NiklasBr commentedon Feb 27, 2024
I'll open a new issue for the Too many open files issue, for what it worth I think my original reported issue is solved, thanks!
lawxen commentedon May 11, 2024
I got the "Too many open files" on debian based image and "No file descriptors available" on alpine based image from docker mac 4.29 and 4.30
@NiklasBr Is there a new issue about this, I didn't find it.