wardenenv / images Goto Github PK

It would be awesome, if Xvfb could be included by default.
Currently, it is not possible to run cypress inside the warden shell, as this system dependency is missing.
You get the following error message, whey you try it:

Your system is missing the dependency: Xvfb

Install Xvfb and run Cypress again.

Read our documentation on dependencies for more information:

https://on.cypress.io/required-dependencies

If you are using Docker, we provide containers with all required dependencies installed.

----------

Error: spawn Xvfb ENOENT

----------

Platform: linux-x64 (CentOS - 9
)
Cypress Version: 13.2.0

As far as I see, this is the only missing dependency, listed on https://docs.cypress.io/guides/getting-started/installing-cypress#Linux-Prerequisites

Could you add Varnish 7.3 to the available Varnish images? Looks like some of the newer Magento versions require Varnish 7.3 (https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/system-requirements.html?lang=en)

v7.3 does not appear in this list (https://hub.docker.com/r/wardenenv/varnish/tags), which only shows up to v7.2. If I try to specify 7.3 in my .env file, then "warden env up" fails.

Thanks!

(If this issue should go to the main Warden repo instead, I'm happy to move it over there.)

After the Podman default resolver was added to the nginx image in 70be181, the DNS resolution seems broken when running in Docker.

When browsing pages in the the Warden environment, the requests would (not consistently, but randomly though often) receive a 502 Bad Gateway error from nginx.

Checking the nginx container logs with

# show just the stderr log
docker logs environmentname-nginx-1 -f 1> /dev/null

Would reveal errors like this:

[error] 57#57: *1690 php-fpm could not be resolved (110: Operation timed out), client: 172.25.0.14, server: , request: "GET /foo/ HTTP/1.1", host: "environmentname.test", referrer: "..."
[error] 60#60: *1695 php-fpm could not be resolved (110: Operation timed out), client: 172.25.0.14, server: , request: "GET /foo/ HTTP/1.1", host: "environmentname.test", referrer: "..."
[error] 59#59: *1698 php-fpm could not be resolved (110: Operation timed out), client: 172.25.0.14, server: , request: "GET /foo/ HTTP/1.1", host: "environmentname.test", referrer: "..."

Removing the default Podman DNS resolver IP from /etc/nginx/conf.d/default.conf and reloading the nginx configs with nginx -s reload would completely remove the issue (or at least I could not reproduce it anymore). Adding the Podman IP back to the resolver list caused the problem to appear again.

System Information:

• OS: Ubuntu 22.04.2 LT / Ubuntu 5.15.0-69.76-generic 5.15.87
• Container image: latest wardenenv/nginx:1.16 at the time of writing
• Docker: Docker version 20.10.3, build 48d30b5 (EDIT: also Docker version 23.0.3, build 3e7cbfd)
• docker-compose: Docker Compose version v2.17.2

EDIT: Noticed my Docker was woefully out of date, but the same problem does happen on the newest version too (Docker version 23.0.3, build 3e7cbfd).

When using Blackfire after running warden env pull && warden env up, a warning is shown in Blackfire:

This profile was generated with an outdated Blackfire Probe

So the used version of the Blackfire Probe is 1.86.4, even though the latest version is 1.89.0 according to https://blackfire.io/docs/up-and-running/update.

https://hub.docker.com/r/wardenenv/php-fpm/tags?page=1&name=8.1-magento2-blackfire shows that the Blackfire image has last been pushed six months ago. Sounds suspicious?

Could you please add the check in the nginx default.conf map for xdebug manual initiation parameters? (https://xdebug.org/docs/step_debug#manual-init)
Either $arg_XDEBUG_SESSION or $arg_XDEBUG_SESSION_START is fine.

I've got a case where I need to debug but I can't set the cookie.
Thanks.