bitnami/wordpress
自动构建
Bitnami Secure Image for WordPress是由Bitnami提供的适用于WordPress的安全优化镜像，其集成预配置的安全防护设置、自动漏洞更新机制、SSL证书支持及基础防火墙功能，可有效降低***与数据泄露风险，同时优化服务器资源分配与运行性能，确保WordPress网站快速稳定部署，且兼容主流云平台与本地服务器环境，为用户提供开箱即用的安全可靠建站解决方案。
让 AI 帮你使用轩辕镜像？ · 展开查看说明 · 点击收起说明
如果你使用 DeepSeek、元宝 AI、Copilot、ChatGPT 等 AI 工具，协助配置轩辕镜像、编写 docker pull 命令、修改 Docker Compose 镜像地址、配置镜像加速、排查镜像拉取失败、分析报错日志等问题，请先让 AI 阅读并遵守轩辕镜像的规则文档。
只需在 AI 对话中先发送下面这句话即可：
请先完整阅读并严格遵守以下文档中的全部规则与要求：
https://xuanyuan.cloud/agents.md
在未充分阅读并理解该文档前，不要生成任何命令、配置、修改建议、故障排查方案或技术回答。后续所有输出都必须严格以该文档中的规范为最高优先级执行。查看 agents.md 用法指南与完整示范。国内用户首推 元宝 AI、DeepSeek 的深度思考模式，不推荐豆包 AI；Cursor 等编辑器可在对话 @ 该链接，或加入 User Rules。 若 AI 无法访问外链，可 打开说明文档 复制全文粘贴。文档会随站点更新，复制内容可能过期，建议定期检查。
Bitnami Secure Image for WordPress
WordPress is the world's most popular blogging and content management platform. Powerful yet simple, everyone from students to global corporations use it to build beautiful, functional websites.
https://wordpress.org Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
TL;DR
consoledocker run --name wordpress REGISTRY_NAME/bitnami/wordpress:latest
NOTE This quick setup is only intended for development environments. You are encouraged to change the insecure default credentials and check out the available configuration options in the Environment Variables section for a more secure deployment.
How to deploy WordPress in Kubernetes
Deploying Bitnami applications as Helm Charts is the easiest way to get started with our applications on Kubernetes. Read more about the installation in the https://github.com/bitnami/charts/tree/master/bitnami/wordpress.
Why use a non-root container?
Non-root container images add an extra layer of security and are generally recommended for production environments. However, because they run as a non-root user, privileged tasks are typically off-limits. Learn more about non-root containers https://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-work-with-non-root-containers-index.html.
Supported tags and respective Dockerfile links
Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags https://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-understand-rolling-tags-containers-index.html.
You can see the equivalence between the different tags by taking a look at the tags-info.yaml file present in the branch folder, i.e bitnami/ASSET/BRANCH/DISTRO/tags-info.yaml.
Subscribe to project updates by watching the https://github.com/bitnami/containers.
Get this image
The recommended way to get the Bitnami WordPress Docker Image is to pull the prebuilt image from the https://hub.docker.com/r/bitnami/wordpress.
consoledocker pull REGISTRY_NAME/bitnami/wordpress:latest
To use a specific version, you can pull a versioned tag. You can view the https://hub.docker.com/r/bitnami/wordpress/tags/ in the Docker Hub Registry.
consoledocker pull REGISTRY_NAME/bitnami/wordpress:[TAG]
If you wish, you can also build the image yourself by cloning the repository, changing to the directory containing the Dockerfile and executing the docker build command. Remember to replace the APP, VERSION and OPERATING-SYSTEM path placeholders in the example command below with the correct values.
consolegit clone https://github.com/bitnami/containers.git cd bitnami/APP/VERSION/OPERATING-SYSTEM docker build -t REGISTRY_NAME/bitnami/APP:latest .
How to use this image
WordPress requires access to a MySQL or MariaDB database to store information. We'll use the https://github.com/bitnami/containers/tree/main/bitnami/mariadb for the database requirements.
Persisting your application
If you remove the container all your data will be lost, and the next time you run the image the database will be reinitialized. To avoid this loss of data, you should mount a volume that will persist even after the container is removed.
For persistence you should mount a directory at the /bitnami/wordpress path. If the mounted directory is empty, it will be initialized on the first run. Additionally you should https://github.com/bitnami/containers/blob/main/bitnami/mariadb#persisting-your-database.
To avoid inadvertent removal of volumes, you can https://docs.docker.com/engine/tutorials/dockervolumes/. Alternatively you can make use of volume plugins to host the volume data.
NOTE Because this is a non-root container, the mounted files and directories must have the proper permissions for the UID
1001.
Configuration
The following section describes environment variables and FIPS configuration.
Environment variables
The following tables list the main variables you can set.
Customizable environment variables
| Name | Description | Default Value |
|---|---|---|
WORDPRESS_DATA_TO_PERSIST | Files to persist relative to the WordPress installation directory. To provide multiple values, separate them with a whitespace. | wp-config.php wp-content |
WORDPRESS_ENABLE_HTTPS | Whether to enable HTTPS for WordPress by default. | no |
WORDPRESS_BLOG_NAME | WordPress blog name. | "User's blog" |
WORDPRESS_SCHEME | Scheme to generate application URLs. Deprecated by WORDPRESS_ENABLE_HTTPS. | http |
WORDPRESS_HTACCESS_OVERRIDE_NONE | Set the Apache AllowOverride variable to None. All the default directives will be loaded from /opt/bitnami/wordpress/wordpress-htaccess.conf. | yes |
WORDPRESS_ENABLE_HTACCESS_PERSISTENCE | Persist the custom changes of the htaccess. It depends on the value of WORDPRESS_HTACCESS_OVERRIDE_NONE, when yes it will persist /opt/bitnami/wordpress/wordpress-htaccess.conf if no it will persist /opt/bitnami/wordpress/.htaccess. | no |
WORDPRESS_RESET_DATA_PERMISSIONS | Force resetting ownership/permissions on persisted data when initializing, otherwise it assumes the ownership/permissions are correct. Ignored when running as non-root. | no |
WORDPRESS_TABLE_PREFIX | Table prefix to use in WordPress. | wp_ |
WORDPRESS_PLUGINS | List of WordPress plugins to install and activate, separated via commas. Can also be set to all to activate all currently installed plugins, or none to skip. | none |
WORDPRESS_EXTRA_INSTALL_ARGS | Extra flags to append to the WordPress 'wp core install' command call. | nil |
WORDPRESS_EXTRA_CLI_ARGS | Extra flags to append to all WP-CLI command calls. | nil |
WORDPRESS_EXTRA_WP_CONFIG_CONTENT | Extra configuration to append to wp-config.php during install. | nil |
WORDPRESS_SKIP_BOOTSTRAP | Whether to perform initial bootstrapping for the application. | no |
WORDPRESS_AUTO_UPDATE_LEVEL | Level of auto-updates to allow for the WordPress core installation. Valid values: major, minor, none. | none |
WORDPRESS_AUTH_KEY | Value of the AUTH_KEY | nil |
WORDPRESS_SECURE_AUTH_KEY | Value of the SECURE_AUTH_KEY | nil |
WORDPRESS_LOGGED_IN_KEY | Value of the LOGGED_IN_KEY | nil |
WORDPRESS_NONCE_KEY | Value of the NONCE_KEY | nil |
WORDPRESS_AUTH_SALT | Value of the AUTH_SALT | nil |
WORDPRESS_SECURE_AUTH_SALT | Value of the SECURE_AUTH_SALT | nil |
WORDPRESS_LOGGED_IN_SALT | Value of the LOGGED_IN_SALT | nil |
WORDPRESS_NONCE_SALT | Value of the NONCE_SALT | nil |
WORDPRESS_ENABLE_REVERSE_PROXY | Enable WordPress support for reverse proxy headers | no |
WORDPRESS_ENABLE_XML_RPC | Enable the WordPress XML-RPC endpoint | no |
WORDPRESS_USERNAME | WordPress user name. | user |
WORDPRESS_PASSWORD | WordPress user password. | bitnami |
WORDPRESS_EMAIL | WordPress user e-mail address. | user@example.com |
WORDPRESS_FIRST_NAME | WordPress user first name. | UserName |
WORDPRESS_LAST_NAME | WordPress user last name. | LastName |
WORDPRESS_ENABLE_MULTISITE | Enable WordPress Multisite configuration. | no |
WORDPRESS_MULTISITE_NETWORK_TYPE | WordPress Multisite network type to enable. Valid values: subfolder, subdirectory, subdomain. | subdomain |
WORDPRESS_MULTISITE_EXTERNAL_HTTP_PORT_NUMBER | External HTTP port for WordPress Multisite. | 80 |
WORDPRESS_MULTISITE_EXTERNAL_HTTPS_PORT_NUMBER | External HTTPS port for WordPress Multisite. | 443 |
WORDPRESS_MULTISITE_HOST | WordPress hostname/address. Only used for Multisite installations. | nil |
WORDPRESS_MULTISITE_ENABLE_NIP_IO_REDIRECTION | Whether to enable IP address redirection to nip.io wildcard DNS when enabling WordPress Multisite. This is only supported when running on an IP address with subdomain network type. | no |
WORDPRESS_MULTISITE_FILEUPLOAD_MAXK | Maximum upload file size allowed for WordPress Multisite uploads, in kilobytes. | 81920 |
WORDPRESS_SMTP_HOST | WordPress SMTP server host. | nil |
WORDPRESS_SMTP_PORT_NUMBER | WordPress SMTP server port number. | nil |
WORDPRESS_SMTP_USER | WordPress SMTP server user. | nil |
WORDPRESS_SMTP_FROM_EMAIL | WordPress SMTP from email. | ${WORDPRESS_SMTP_USER} |
WORDPRESS_SMTP_FROM_NAME | WordPress SMTP from name. | ${WORDPRESS_FIRST_NAME} ${WORDPRESS_LAST_NAME} |
WORDPRESS_SMTP_PASSWORD | WordPress SMTP server user password. | nil |
WORDPRESS_SMTP_PROTOCOL | WordPress SMTP server protocol to use. | nil |
WORDPRESS_DATABASE_HOST | Database server host. | $WORDPRESS_DEFAULT_DATABASE_HOST |
WORDPRESS_DATABASE_PORT_NUMBER | Database server port. | 3306 |
WORDPRESS_DATABASE_NAME | Database name. | bitnami_wordpress |
WORDPRESS_DATABASE_USER | Database user name. | bn_wordpress |
WORDPRESS_DATABASE_PASSWORD | Database user password. | nil |
WORDPRESS_ENABLE_DATABASE_SSL | Whether to enable SSL for database connections. | no |
WORDPRESS_VERIFY_DATABASE_SSL | Whether to verify the database SSL certificate when SSL is enabled for database connections. | yes |
WORDPRESS_DATABASE_SSL_CERT_FILE | Path to the database client certificate file. | nil |
WORDPRESS_DATABASE_SSL_KEY_FILE | Path to the database client certificate key file. | nil |
WORDPRESS_DATABASE_SSL_CA_FILE | Path to the database server CA bundle file. | nil |
WORDPRESS_OVERRIDE_DATABASE_SETTINGS | Override the database settings in persistence. | no |
Read-only environment variables
| Name | Description | Value
Note: the README for this container is longer than the DockerHub length limit of 25000, so it has been trimmed. The full README can be found at https://techdocs.broadcom.com/us/en/vmware-tanzu/bitnami-secure-images/bitnami-secure-images/services/bsi-app-doc/apps-containers-wordpress-index.html
镜像拉取方式
您可以使用以下命令拉取该镜像。请将 <标签> 替换为具体的标签版本。如需查看所有可用标签版本，请访问 标签列表页面。
轩辕镜像加速拉取命令点我查看更多 wordpress 镜像标签
docker pull docker.xuanyuan.run/bitnami/wordpress:<标签>
DockerHub 原生拉取命令
docker pull bitnami/wordpress:<标签>
镜像拉取常见问题
功能
错误码
用户好评
来自真实用户的反馈，见证轩辕镜像的优质服务
oldzhang
运维工程师
Linux服务器
5
"Docker访问体验非常流畅，大镜像也能快速完成下载。"