-
Notifications
You must be signed in to change notification settings - Fork 116
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
rosetta error: futex(FUTEX_LOCK_PI_PRIVATE) failure: 35 - os x 13.2.1 (ventura). rosetta 2 #7037
Comments
This also happens in Mac OS 14.1 Sonoma:
FROM php:8.1-cli
COPY --from=composer:latest /usr/bin/composer /usr/bin/composer
ENTRYPOINT ["/usr/local/bin/docker-entrypoint.sh"]
CMD ["bash"] Docker info:
Diagnostics ID
|
Well that's today's best laugh! |
It looks like Orbstack was able to fix this, maybe it is time to migrate? |
Hi @NiklasBr, do you have a sample command that triggers the issue? |
Create a Dockerfile using the example I posted above, then run any Composer command |
@dgageot related and another example of the same thing I think: #6887 (comment) |
@NiklasBr sorry, I don't know compose enough to trigger an issue. Do I need a sample |
I've tried a
I probably need something more complex. |
Looks like maybe you are on an amd64 architecture and not arm64? You don't even need to install anything just like me and the other people are saying,: You can run composer without any arguments whatsoever and reproduce the issue 100% of the time. You can make it less complex. |
Thanks @NiklasBr for the details. Although that’s not my experience. I can’t make it fail no matter what I do |
Again, make sure the docker image is not an ARM architecture. Then, make sure you are using Rosetta. It's really as simple as that. I can't wrap my head around why you can't reproduce it. Many of us are able to do it with 100% rate, and it has followed along with many updates of both Docker Desktop and the Mac OS operating system. |
Yes, all of that I have... Some of the Rosetta issues were fixed in Sonoma 14.1. Which version of macOS do you have? |
Sonoma 14.1 as mentioned a few weeks ago on an M1 Max CPU. My experience is that Rosetta still works exactly as problematic as it did with Mac OS 13.6. |
I'm on Sonoma 14.1, with a Mac M1 Pro and a Mac M2 Pro. Can't reproduce on any of the last five Docker Desktop versions. I've tried things more complicated than that but can you tell me if this simple command fails for you?
|
You need to use and AMD64 image and use Rosetta..... |
Yeah. That's what I've been doing. I'm sorry to insist but if nobody can give me a command that reproduces the issue, I'll be forced to close this ticket. |
Your command and setup obviously does not trigger it. I repeat, the way to trigger it, as mentioned earlier, is to enable Rosetta in Docker Desktop settings, then run an AMD64 image using the following command on an ARM Mac: |
@dgageot I am facing the same issue on Mac OS Sonoma 14.1 running on Mac pro m2 chip.
![]()
![]()
Result: My docker info: Client: Server: WARNING: daemon is not using the default seccomp profile Docker Desktop Version: 4.25.1 Please let me know if you have any questions. |
Thanks a lot @jumakiwaka. Using your precise instructions, I was able to reproduce. One way to reproduce it even faster is to run:
and then, simply:
I tried to combine those two commands in one but this doesn't fail:
EDIT: It doesn't fail with the stock
|
Here's a simpler way to reproduce: Build a php image with opcache enabled:
Run the image:
Type the faulty command:
This fails with php |
@jumakiwaka could you try to add this to
|
Looks like a fix / improvement was made in Docker Desktop, which will ship with the next release |
Do we know which version includes the fix? I just upgraded to Docker Desktop DockerfileFROM --platform=linux/amd64 grafana/k6
USER root
RUN apk update Notes
Build
System
|
Well I found a workaround. This works for my case: FROM --platform=linux/amd64 grafana/k6
USER root
RUN apk upgrade -U (My real use case calls This all seems very non-deterministic to me though. I'll be interested to hear where it lands. |
Hi @matsaleh13, a similar issue was fixed with php in Docker Desktop 4.26.0. |
Ohh... do you know whether Apple will backport the fix to Ventura? I guess they're not known too well for that kind of thing, right? Well, thanks for clarifying that, and thanks for the prompt response! |
Indeed. I don't think they will |
I'm going to close this issue. Feel free to reopen if you manage to reproduce on a recent macOS. |
This just occurred to me on Mac OS X Sonoma 14.3 when installing PHP FPM 8.1 from the Steps to recreate:Create the following Dockerfile:FROM ubuntu:latest
RUN set -eu; \
#
apt-get update; \
#
# Configure ondrej PPA
apt-get install -y software-properties-common; \
add-apt-repository ppa:ondrej/php; \
apt-get update; \
#
# Install PHP
apt-get install -y --no-install-recommends php8.1-fpm; \
#
# Make sure everything works
php-fpm8.1 -v Run the following command:docker buildx build --platform linux/amd64 . System info:Docker settings: |
Thanks a lot @Chekote, I'm giving it a try right now |
@Chekote a fix is one the way. I might be included in Docker Desktop 4.27.1 hot fix. |
@dgageot awesome! Thanks for the amazingly fast resolution ❤️ |
What happened is that in 4.26, we removed the support for Huge Tables that caused issues with php. This was a bit too brutal of a fix but php users were happy. In 4.27, we put back Huge Tables and added a targeted fix for |
Hi @Chekote! Docker Desktop 4.27.1 is out. Could you tell me if it solves your issue? |
Just updated to
|
@dgageot 4.27.1 is a security release for the runc and buildkit advisories; other patches/fixes will now be in 4.27.2 (next week) |
Rolling back to 4.26.1 appears to resolve the issue I mentioned above for me, for now. Btw, I noticed the date on the release notes for 4.27.1 is accidentally showing 2023-02-01 instead of 2024-02-01, just a heads up :) |
Good catch! Looks like someone fixed it ❤️ docker/docs#19289 Also apologies for the confusion for the 4.27.1 release not having these patches; these patches (fixes) were merged already, but the embargoed security took priority, and it's generally good practice not to combine regular fixes with a security release, to prevent possible regressions (which may prevent users from being able to use the security fixes). |
Unfortunately it doesn't. I still see the problem |
Hi @Chekote, @eolivelli and @Chekote! |
I still have PHP-FPM issues in 4.27.2: #7182 Not sure if it is actually Rosetta… But the effect is that 4.27.x is still not stable enough on ARM Mac:s to get an environment up and running :( |
Temporary fix (worked for me on M1 mac):
|
Building with |
@dgageot 4.27.2 resolved the problem I reported earlier. I am performing some more builds just to be sure. I'll keep you posted. |
@dgageot I was able to build many PHP images for many projects, both CLI and FPM, for PHP versions 8.1.27, 8.2.15, and 8.3.2 without any problems. |
Description
running
docker compose up
ordocker build
with a multi-stage golang image results in the following error:(container and binary names elided)
I've uninstalled and reinstalled docker desktop.
pruning docker cache, volumes, containers makes no difference.
Docker desktop configured to use VirtioFS, Rosetta for x86/amd64 emulation on Apple Silicon also enabled
Reproduce
docker build
ordocker compose up
Expected behavior
Should build without error
docker version
Client: Cloud integration: v1.0.35+desktop.5 Version: 24.0.6 API version: 1.43 Go version: go1.20.7 Git commit: ed223bc Built: Mon Sep 4 12:28:49 2023 OS/Arch: darwin/arm64 Context: desktop-linux Server: Docker Desktop 4.24.2 (124339) Engine: Version: 24.0.6 API version: 1.43 (minimum version 1.12) Go version: go1.20.7 Git commit: 1a79695 Built: Mon Sep 4 12:31:36 2023 OS/Arch: linux/arm64 Experimental: false containerd: Version: 1.6.22 GitCommit: 8165feabfdfe38c65b599c4993d227328c231fca runc: Version: 1.1.8 GitCommit: v1.1.8-0-g82f18fe docker-init: Version: 0.19.0 GitCommit: de40ad0
docker info
Diagnostics ID
3C38E6D2-EFDE-497A-A98F-F21E86BD5F82/20231020023245
Additional Info
MacBook Pro
Apple M2
8 Gb memory
OS: ventura (13.2.1)
The text was updated successfully, but these errors were encountered: