You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apparently, using export in .env files was never supported by Docker, and now it's broken. The fix seemed self-explanatory, remove all occurrences of export from the .env file, which allowed the containers to boot.
After that I was stuck in this screen:
I did some more debugging, and found out that parse_url fails in config/wp-config.php, because the value it tried to parse looked like this: mysql://wordpress:password@$DATABASE_HOST:$DATABASE_PORT/wordpress
I'm guessing replace stopped working after removing the exports from the .env file. I got everything running again by rewriting the DATABASE_URL & REDIS_URL variables to these:
I'm using Arch, so I'm always using the latest versions of everything. Last week, after updating, all of my projects using this stopped working.
After a brief debugging session, I found this: docker/compose#6511
Apparently, using
export
in .env files was never supported by Docker, and now it's broken. The fix seemed self-explanatory, remove all occurrences ofexport
from the .env file, which allowed the containers to boot.After that I was stuck in this screen:

I did some more debugging, and found out that parse_url fails in config/wp-config.php, because the value it tried to parse looked like this:
mysql://wordpress:password@$DATABASE_HOST:$DATABASE_PORT/wordpress
I'm guessing replace stopped working after removing the
export
s from the .env file. I got everything running again by rewriting the DATABASE_URL & REDIS_URL variables to these:The text was updated successfully, but these errors were encountered: