-
Notifications
You must be signed in to change notification settings - Fork 29
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
Issue running the container download with Docker for Windows #6
Comments
Sorry should have said "using the git clone command, however...." instead of "using the however" on line 5. |
I'm not sure, but I will tag @TRPB and see if he can offer any guidance here. |
I've had this occasionally when PECL is down (it's not got a great track record for uptime), can you try again now some time has passed? |
I tried several times but the thing that has worked is to use a computer running Linux Mint. |
This is entirely a network issue so unlikely to be fixed by swapping OS unless some OS level network setting is blocking PECL or PECL is blocking your connection (vpn, proxy, etc) |
I have had to go a fresh install of docker as I am now constantly getting a failed to initialise warning. |
Hi,
I am using a Windows 10 PC, with Docker for Windows (v4.20.1), Git (2.40.1.windows.1) and WSL (version 1.2.5.0) with kernel (version 5.15.90.1) and following the instructions in the book.
all downloads appear to run without any problems, using the however when running the command docker compose up I get the error
=> [php stage-0 4/16] RUN apk add --no-cache linux-headers
=> ERROR [php stage-0 5/16] RUN pecl install xdebug
------
> [php stage-0 5/16] RUN pecl install xdebug:
#0 5.551 No releases available for package "pecl.php.net/xdebug"
#0 5.551 install failed
------
failed to solve process "/bin/sh -c pecl install xdebug" did not complete successfully: exit code: 1
I am unsure if this is an issue due to windows or from within the downloaded docker container?
I would appreciate any guidance on what the issue could be.
Regards,
P
The text was updated successfully, but these errors were encountered: