|
|
@@ -215,11 +215,16 @@ The simplest way to use it with an existing WordPress container would be somethi
|
|
|
$ docker run -it --rm \
|
|
|
--volumes-from some-wordpress \
|
|
|
--network container:some-wordpress \
|
|
|
+ -e WORDPRESS_DB_USER=... \
|
|
|
+ -e WORDPRESS_DB_PASSWORD=... \
|
|
|
+ # [and other used environment variables]
|
|
|
wordpress:cli user list
|
|
|
```
|
|
|
|
|
|
Generally speaking, for WP-CLI to interact with a WordPress install, it needs access to the on-disk files of the WordPress install, and access to the database (and the easiest way to accomplish that such that `wp-config.php` does not require changes is to simply join the networking context of the existing and presumably working WordPress container, but there are many other ways to accomplish that which will be left as an exercise for the reader).
|
|
|
|
|
|
+**NOTE:** Since March 2021, WordPress images use a customized `wp-config.php` that pulls the values directly from the environment variables defined above (see `wp-config-docker.php` in [docker-library/wordpress#572](https://github.com/docker-library/wordpress/pull/572) and [docker-library/wordpress#577](https://github.com/docker-library/wordpress/pull/577)). As a result of reading environment variables directly, the cli container also needs the same set of environment variables to properly evaluate `wp-config.php`.
|
|
|
+
|
|
|
# License
|
|
|
|
|
|
View [license information](https://wordpress.org/about/license/) for the software contained in this image.
|
Docker Library Bot