-
Notifications
You must be signed in to change notification settings - Fork 476
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
Error response from daemon: lease moby-image-sha256:XXXXXXXXX not found #597
Comments
Fairly sure this isn't a sail issue - it's to do with not having rosetta running on my M2 macbook. I'll close for now and do some further testing. |
I'll leave this open for a bit to see if others report the same but also fairly sure this is a network, downstream issue or temp hiccup. |
@driesvints I think it's a Docker 4.21 issue - got the same happening on other images as well. |
..and other machines running 4.21 as well. |
Think it's safe to say then that this isn't a Sail issue @ssx? |
Yeah - I think it's some combination of newer Docker versions and Rosetta. I don't have Rosetta on my home macbook and can't get sail to run at all. I'd imagine non-arm Mac's don't have this issue at all. Work mac, I can build and run on Docker 14.5 but not the later versions (will do some more testing). |
Narrowed this down somewhat. It's definitely an Apple Silicon issue more than anything else. By default, the problem seems to be newer versions of Docker are building linux/arm64 images when they should be linux/amd64. If the platform is set in the FROM label of the Dockerfile, it solves this problem:
This appears to solve the problem and all the containers run as expected (even in newer Docker versions). What I think is happening is that during the build process, it's losing the platform somewhere and then generates a parent image with the wrong platform. When they're built as default as linux/arm64 it then can't find the parent. |
So, I know what this is now. On an M1/M2 Mac - to make this work properly in newer Docker versions without modifying anything in Sail, you will need to run this first:
If you don't do this first, what happens is Docker pulls a When you then run which I think is because some of the services are running as When you try to build purely as So, to solve, run:
then carry on as usual running |
Glad you solved that 👍 |
Sail Version
1.23.1
Laravel Version
10.16.1
PHP Version
8.2
Operating System
macOS
OS Version
14.0
Description
Bit of an odd one here.
When installing Sail into a blank app, I'm getting the following error when running
sail up
:Error response from daemon: lease "moby-image-sha256:6936624d0c533c751ae6e6a4e7e1e82cc6e37945a3807b063d457da21c1e24d9": not found
I'm not entirely sure this is a sail issue - I think it may be a Docker/Apple SIlicon issue instead.
Is this something you folks have seen or had other reports of?
Steps To Reproduce
Install blank project, install sail, sail up.
The text was updated successfully, but these errors were encountered: