This repository has been archived by the owner on May 9, 2024. It is now read-only.
10updocker wp snapshots
is not recognized as a registered wp command on WSL2
#347
Labels
bug
Something isn't working
Troubleshooting
Describe the bug
On WSL2 (Ubuntu), I had some trouble working with snapshots and
v.4.*
ofwp-local-docker-v2
.I tested this on a clean install on a new machine, so I've installed v.4.0.0 directly (no upgrade from previous version). When I try to run any
10updocker wp snapshots
command, I get the error:I tried running
10updocker image update
, as well as updatingdocker-compose.yml
as per the instructions, but the same error persisted. I tried running different image configurations, like for example running it from sites with different PHP versions, but I always got the same error.It's worth noting that Ubuntu suffixes the images with my WSL username (which is
gsarig
), so at first, when I checked my image indocker-compose.yml
, it looked like this:wp-php-fpm-dev-8.0-gsarig
. When I ran10updocker image update
, the update ran, but I got a message like:To fix it, I ran
docker pull 10up/wp-php-fpm:8.0-ubuntu
to pull the PHP image, and then manually updatedocker-compose.yml
to use it.Still this had no effect, as I kept getting the same error every time I tried to run
10updocker wp snapshots
(that it's not a registered command).After failing to set it up, I tried to use the old
wpsnapshots
with v.4 ofwp-local-docker
. While it works fine when it comes to connecting, finding and pulling the snapshots, it failed to actually set up the snapshot. The message I got, during the setup, was this:I believe that it's because it tries to connect with the server's php and not with the container's. If I try to run it with
10updocker wpsnapshots pull
, I get the earlier error:In the end, I had to downgrade to v3, in order to be able to use the old snapshots.
Steps to Reproduce
wp-local-docker-v2
10updocker wp snapshots
in it using any command.Screenshots, screen recording, code snippet
No response
Environment information
Code of Conduct
The text was updated successfully, but these errors were encountered: