[dev-env] Wordpress container not initiating

[Antonio-Laguna]

After updating Docker (I'm on Docker version 29.0.1, build eedd969) the WordPress container won't start. I have several projects and all started doing the same after the update.

If I manually try to start the container, I get this error from the container's logs

rsync: [generator] delete_file: rmdir(vip-config) failed: Permission denied (13)
rsync: [generator] delete_file: rmdir(log) failed: Permission denied (13)
rsync: [generator] delete_file: rmdir(config) failed: Permission denied (13)
rsync: [generator] delete_file: rmdir(wp-content/uploads) failed: Permission denied (13)
rsync: [generator] delete_file: rmdir(wp-content/themes) failed: Permission denied (13)
rsync: [generator] delete_file: rmdir(wp-content/private) failed: Permission denied (13)
rsync: [generator] delete_file: rmdir(wp-content/plugins) failed: Permission denied (13)
rsync: [generator] delete_file: rmdir(wp-content/languages) failed: Permission denied (13)
rsync: [generator] delete_file: rmdir(wp-content/images) failed: Permission denied (13)
rsync: [generator] delete_file: rmdir(wp-content/client-mu-plugins) failed: Permission denied (13)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1338) [sender=3.3.0]

I've tried shelling and checking permissions, but couldn't see anything obvious there.

vip is 3.21.2

[sjinks]

Could you please share your ~/.local/share/vip/dev-environment/<env name>/vip-local/instance_data.json and ~/.local/share/vip/dev-environment/<env name>/vip-local/lando.yml?

And the output of

docker image ls | grep ghcr.io/automattic/vip-container-images

so that we know which versions of the images are in use.

[dero-newsuk]

Docker 29 breaks Traefik, which VIP CLI uses. I had to rollback.

https://forums.docker.com/t/docker-29-increased-minimum-api-version-breaks-traefik-reverse-proxy/150384

cc @sjinks

[sjinks]

@dero-newsuk that was addressed in #2637 and Automattic/lando-cli#128.

tl;dr: you need to update VIP CLI, then stop all your dev environments (this will shut down the proxy container), then start them. Traefik will be automatically updated, and this will resolve your issue.

[john-jeeves-americaneagle]

Updated to VIP version 3.22.5 and nginx is down and wordpress container is killed. Ive destroyed and rebuilt but still same error:

Error response from daemon: container 3a9bc93109021cac9b4dd888b7f3406a4671e1e26f3ef35057720396323f9809 is not running
ERROR ==> /usr/bin/docker,compose,--project-name,wpdev,--file,/home/user/.local/share/vip/lando/compose/wpdev/globals-0.yml,--file,/home/user/.local/share/vip/lando/compose/wpdev/mounts-0.yml,--file,/home/user/.local/share/vip/lando/compose/wpdev/nginx-0.yml,--file,/home/user/.local/share/vip/lando/compose/wpdev/nginx-1.yml,--file,/home/user/.local/share/vip/lando/compose/wpdev/nginx-2.yml,--file,/home/user/.local/share/vip/lando/compose/wpdev/php-0.yml,--file,/home/user/.local/share/vip/lando/compose/wpdev/php-1.yml,--file,/home/user/.local/share/vip/lando/compose/wpdev/php-2.yml,--file,/home/user/.local/share/vip/lando/compose/wpdev/database-0.yml,--file,/home/user/.local/share/vip/lando/compose/wpdev/database-1.yml,--file,/home/user/.local/share/vip/lando/compose/wpdev/database-2.yml,--file,/home/user/.local/share/vip/lando/compose/wpdev/memcached-0.yml,--file,/home/user/.local/share/vip/lando/compose/wpdev/memcached-1.yml,--file,/home/user/.local/share/vip/lando/compose/wpdev/memcached-2.yml,--file,/home/user/.local/share/vip/lando/compose/wpdev/phpmyadmin-0.yml,--file,/home/user/.local/share/vip/lando/compose/wpdev/phpmyadmin-1.yml,--file,/home/user/.local/share/vip/lando/compose/wpdev/phpmyadmin-2.yml,--file,/home/user/.local/share/vip/lando/compose/wpdev/elasticsearch-0.yml,--file,/home/user/.local/share/vip/lando/compose/wpdev/elasticsearch-1.yml,--file,/home/user/.local/share/vip/lando/compose/wpdev/elasticsearch-2.yml,--file,/home/user/.local/share/vip/lando/compose/wpdev/wordpress-0.yml,--file,/home/user/.local/share/vip/lando/compose/wpdev/wordpress-1.yml,--file,/home/user/.local/share/vip/lando/compose/wpdev/wordpress-2.yml,--file,/home/user/.local/share/vip/lando/compose/wpdev/vip-mu-plugins-0.yml,--file,/home/user/.local/share/vip/lando/compose/wpdev/vip-mu-plugins-1.yml,--file,/home/user/.local/share/vip/lando/compose/wpdev/vip-mu-plugins-2.yml,--file,/home/user/.local/share/vip/lando/compose/wpdev/mailpit-0.yml,--file,/home/user/.local/share/vip/lando/compose/wpdev/mailpit-1.yml,--file,/home/user/.local/share/vip/lando/compose/wpdev/mailpit-2.yml,--file,/home/user/.local/share/vip/lando/compose/wpdev/photon-0.yml,--file,/home/user/.local/share/vip/lando/compose/wpdev/photon-1.yml,--file,/home/user/.local/share/vip/lando/compose/wpdev/photon-2.yml,--file,/home/user/.local/share/vip/lando/compose/wpdev/proxy-0.yml,--file,/home/user/.local/share/vip/lando/compose/wpdev/proxy-1.yml,--file,/home/user/.local/share/vip/lando/compose/wpdev/proxy-2.yml,exec,--detach,--env,PHP_MEMORY_LIMIT=-1,--user,root,photon,/bin/sh,-c,mkdir-p /certs && /helpers/refresh-certs.sh > /certs/refresh.log failed with exit code 1

HEALTH WARNINGS    The following services have failed health checks:
nginx

[sjinks]

@john-jeeves-americaneagle could you please paste the output of vip dev-env logs --slug=wpdev?

Also, is there anything running on port 80 or 443 on your host?

[john-jeeves-americaneagle]

Looks to me to just be the dev env:
tcp 0 0 127.0.0.1:80 0.0.0.0:* LISTEN -
tcp 0 0 127.0.0.1:443 0.0.0.0:* LISTEN -

if i stop the dev env, nothing is on those ports.

Attached is log file.

wpdev.log

[matfantinel]

Just wanted to add that I'm having the same issue on mine and rolling back to Docker v28 didn't do anything. My logs look very similar to @john-jeeves-americaneagle

This is the output of docker image ls | grep ghcr.io/automattic/vip-container-images:

ghcr.io/automattic/vip-container-images/mu-plugins:0.1       bbdaa8449427        695MB          192MB   U    
ghcr.io/automattic/vip-container-images/nginx:latest         811d4c1613d4       91.1MB         25.1MB   U    
ghcr.io/automattic/vip-container-images/photon:latest        b65d20d26d0b        111MB         32.2MB   U    
ghcr.io/automattic/vip-container-images/php-fpm:8.2          588cd06c0c2c        874MB          200MB   U    
ghcr.io/automattic/vip-container-images/traefik_openssl:v3   295e69d1f071        227MB         48.8MB   U    
ghcr.io/automattic/vip-container-images/wordpress:6.9        cc57db7c2cb7        121MB         25.5MB   U 

[sjinks]

@john-jeeves-americaneagle this will be fixed in Automattic/vip-container-images#1359

[sjinks]

@john-jeeves-americaneagle please run

vip dev-env update --slug=wptest < /dev/null
vip dev-env start --slug=wptest

The first command will force the dev env to update the images to pull in the fix, and the second will restart the environment.

[john-jeeves-americaneagle]

@john-jeeves-americaneagle please run

vip dev-env update --slug=wptest < /dev/null
vip dev-env start --slug=wptest

The first command will force the dev env to update the images to pull in the fix, and the second will restart the environment.

Works, thanks @sjinks