[{"_1":2,"_141":-5,"_142":-5},"loaderData",{"_3":4,"_17":18,"_24":25,"_135":136},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7,"_13":14,"_15":16},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","theme","system","contrast","normal","routes/_layout",{"_19":-5,"_20":21,"_22":11,"_23":21},"username","isAskGordonEnabled",true,"showMinimalLanding","showHoneypotTrap","routes/_layout.layers.$namespace.$reponame.$tag.(images).($imageUrlDigest)",{"_26":27,"_28":29,"_58":59,"_60":-7,"_61":-7,"_62":-7,"_63":-7,"_64":-5,"_65":-5,"_66":11,"_67":11,"_51":68,"_124":21,"_92":93,"_125":91,"_126":50,"_34":35,"_127":11,"_128":21,"_129":130,"_131":-5,"_132":11,"_133":11,"_134":11},"scanningType","none","tagData",{"_30":31,"_32":33,"_34":35,"_36":37,"_38":39,"_40":41,"_42":43,"_44":33,"_45":46,"_47":48,"_49":50,"_51":52,"_53":-5,"_54":43,"_55":56,"_57":21},"content_type","image","creator",35095401,"digest","sha256:2df9fcd1863427fe7eb780257f594ecebcac7f254e4641661eb5d4f541cfc129","full_size",255,"id",1371688366,"images",[],"last_updated","2026-10-28T21:36:16.161934Z","last_updater","last_updater_username","bitnamibot508","media_type","application/vnd.oci.image.config.v1+json","name","sha256-4b1c708beb68ebff5382c0d4a21c2cb0c12fd3f1bdfcfe8a3c612629a655cfac.sig","repository",331794,"tag_last_pulled","tag_last_pushed","tag_status","active","v2","tagImages",[],"layerOrdinals","packageName","cveId","sbom","scoutSummary","staticSummary","isScoutPaymentRequired","canSeeVulnerabilities",{"_69":70,"_75":76,"_78":79,"_80":81,"_82":11,"_42":83,"_84":85,"_86":87,"_49":91,"_92":93,"_94":95,"_96":31,"_97":98,"_99":100,"_101":56,"_102":-5,"_103":104,"_105":106,"_107":11,"_108":93,"_109":110,"_115":21,"_116":117,"_121":93,"_122":123},"categories",[71],{"_49":72,"_73":74},"Content management system","slug","content-management-system","content_types",[31,77],"unrecognized","date_registered","2015-09-22T15:34:22.310718Z","description","Bitnami Secure Image for wordpress","is_private","2026-11-04T12:42:00.337633Z","last_modified","2026-09-22T08:07:02.437944Z","media_types",[88,48,89,90],"application/vnd.docker.distribution.manifest.list.v2+json","application/vnd.oci.image.index.v1+json","application/vnd.vmware.tac.metadata.config.v1+json","wordpress","namespace","bitnami","pull_count",110253999,"repository_type","star_count",284,"status",1,"status_description","source","collaborator_count",0,"full_description","# Bitnami Secure Image for WordPress\n\n> 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.\n\n[Overview of WordPress](https://wordpress.org)\nTrademarks: 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.\n\n## TL;DR\n\n```console\ndocker run --name wordpress REGISTRY_NAME/bitnami/wordpress:latest\n```\n\n> Note: You need to substitute the `REGISTRY_NAME` placeholder with a reference to your container registry.\n\n## Using `docker-compose.yml`\n\nThe docker-compose.yaml file of this container can be found in the [Bitnami Containers repository](https://github.com/bitnami/containers/).\n\n[https://github.com/bitnami/containers/tree/main/bitnami/wordpress/docker-compose.yml](https://github.com/bitnami/containers/tree/main/bitnami/wordpress/docker-compose.yml)\n\nPlease be aware this file has not undergone internal testing. Consequently, we advise its use exclusively for development or testing purposes. For production-ready deployments, we highly recommend utilizing its associated [Bitnami Helm chart](https://github.com/bitnami/charts/tree/main/bitnami/wordpress).\n\n## How to deploy WordPress in Kubernetes\n\nDeploying Bitnami applications as Helm Charts is the easiest way to get started with our applications on Kubernetes. Read more about the installation in the [Bitnami WordPress Chart GitHub repository](https://github.com/bitnami/charts/tree/master/bitnami/wordpress).\n\n## Why use a non-root container?\n\nNon-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 [in our docs](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).\n\n## Supported tags and respective `Dockerfile` links\n\nLearn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags [in our documentation page](https://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-understand-rolling-tags-containers-index.html).\n\n## Get this image\n\nThe Bitnami WordPress Docker image is only available to [Bitnami Secure Images](https://bitnami.com) customers.\n\n## How to use this image\n\nWordPress requires access to a MySQL or MariaDB database to store information. We'll use the [Bitnami Docker Image for MariaDB](https://github.com/bitnami/containers/tree/main/bitnami/mariadb) for the database requirements.\n\n## Persisting your application\n\nIf 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.\n\nFor 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 [mount a volume for persistence of the MariaDB data](https://github.com/bitnami/containers/blob/main/bitnami/mariadb#persisting-your-database).\n\nTo avoid inadvertent removal of volumes, you can [mount host directories as data volumes](https://docs.docker.com/engine/tutorials/dockervolumes/). Alternatively you can make use of volume plugins to host the volume data.\n\n> **NOTE** Because this is a non-root container, the mounted files and directories must have the proper permissions for the UID `1001`.\n\n## Configuration\n\nThe following section describes environment variables and FIPS configuration.\n\n### Environment variables\n\nThe following tables list the main variables you can set.\n\n#### Customizable environment variables\n\n| Name | Description | Default Value |\n|--------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------|\n| `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` |\n| `WORDPRESS_ENABLE_HTTPS` | Whether to enable HTTPS for WordPress by default. | `no` |\n| `WORDPRESS_BLOG_NAME` | WordPress blog name. | `\"User's blog\"` |\n| `WORDPRESS_SCHEME` | Scheme to generate application URLs. Deprecated by `WORDPRESS_ENABLE_HTTPS`. | `http` |\n| `WORDPRESS_HOSTNAME` | Hostname to generate application URLs. | `nil` |\n| `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` |\n| `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` |\n| `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` |\n| `WORDPRESS_TABLE_PREFIX` | Table prefix to use in WordPress. | `wp_` |\n| `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` |\n| `WORDPRESS_EXTRA_INSTALL_ARGS` | Extra flags to append to the WordPress 'wp core install' command call. | `nil` |\n| `WORDPRESS_EXTRA_CLI_ARGS` | Extra flags to append to all WP-CLI command calls. | `nil` |\n| `WORDPRESS_EXTRA_WP_CONFIG_CONTENT` | Extra configuration to append to wp-config.php during install. | `nil` |\n| `WORDPRESS_SKIP_BOOTSTRAP` | Whether to perform initial bootstrapping for the application. | `no` |\n| `WORDPRESS_AUTO_UPDATE_LEVEL` | Level of auto-updates to allow for the WordPress core installation. Valid values: `major`, `minor`, `none`. | `none` |\n| `WORDPRESS_AUTH_KEY` | Value of the AUTH_KEY | `nil` |\n| `WORDPRESS_SECURE_AUTH_KEY` | Value of the SECURE_AUTH_KEY | `nil` |\n| `WORDPRESS_LOGGED_IN_KEY` | Value of the LOGGED_IN_KEY | `nil` |\n| `WORDPRESS_NONCE_KEY` | Value of the NONCE_KEY | `nil` |\n| `WORDPRESS_AUTH_SALT` | Value of the AUTH_SALT | `nil` |\n| `WORDPRESS_SECURE_AUTH_SALT` | Value of the SECURE_AUTH_SALT | `nil` |\n| `WORDPRESS_LOGGED_IN_SALT` | Value of the LOGGED_IN_SALT | `nil` |\n| `WORDPRESS_NONCE_SALT` | Value of the NONCE_SALT | `nil` |\n| `WORDPRESS_ENABLE_REVERSE_PROXY` | Enable WordPress support for reverse proxy headers | `no` |\n| `WORDPRESS_ENABLE_XML_RPC` | Enable the WordPress XML-RPC endpoint | `no` |\n| `WORDPRESS_USERNAME` | WordPress user name. | `user` |\n| `WORDPRESS_PASSWORD` | WordPress user password. | `nil` |\n| `WORDPRESS_EMAIL` | WordPress user e-mail address. | `user@example.com` |\n| `WORDPRESS_FIRST_NAME` | WordPress user first name. | `UserName` |\n| `WORDPRESS_LAST_NAME` | WordPress user last name. | `LastName` |\n| `WORDPRESS_ENABLE_MULTISITE` | Enable WordPress Multisite configuration. | `no` |\n| `WORDPRESS_MULTISITE_NETWORK_TYPE` | WordPress Multisite network type to enable. Valid values: `subfolder`, `subdirectory`, `subdomain`. | `subdomain` |\n| `WORDPRESS_MULTISITE_EXTERNAL_HTTP_PORT_NUMBER` | External HTTP port for WordPress Multisite. | `80` |\n| `WORDPRESS_MULTISITE_EXTERNAL_HTTPS_PORT_NUMBER` | External HTTPS port for WordPress Multisite. | `443` |\n| `WORDPRESS_MULTISITE_HOST` | WordPress hostname/address. Only used for Multisite installations. | `nil` |\n| `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` |\n| `WORDPRESS_MULTISITE_FILEUPLOAD_MAXK` | Maximum upload file size allowed for WordPress Multisite uploads, in kilobytes. | `81920` |\n| `WORDPRESS_SMTP_HOST` | WordPress SMTP server host. | `nil` |\n| `WORDPRESS_SMTP_PORT_NUMBER` | WordPress SMTP server port number. | `nil` |\n| `WORDPRESS_SMTP_USER` | WordPress SMTP server user. | `nil` |\n| `WORDPRESS_SMTP_FROM_EMAIL` | WordPress SMTP from email. | `${WORDPRESS_SMTP_USER}` |\n| `WORDPRESS_SMTP_FROM_NAME` | WordPress SMTP from name. | `${WORDPRESS_FIRST_NAME} ${WORDPRESS_LAST_NAME}` |\n| `WORDPRESS_SMTP_PASSWORD` | WordPress SMTP server user password. | `nil` |\n| `WORDPRESS_SMTP_PROTOCOL` | WordPress SMTP server protocol to use. | `nil` |\n| `WORDPRESS_DATABASE_HOST` | Database server host. | `$WORDPRESS_DEFAULT_DATABASE_HOST` |\n| `WORDPRESS_DATABASE_PORT_NUMBER` | Database server port. | `3306` |\n| `WORDPRESS_DATABASE_NAME` | Database name. | `bitnami_wordpress` |\n| `WORDPRESS_DATABASE_USER` | Database user name. | `bn_wordpress` |\n| `WORDPRESS_DATABASE_PASSWORD` | Database user password. | `nil` |\n| `WORDPRESS_ENABLE_DATABASE_SSL` | Whether to enable SSL for database connections. | `no` |\n| `WORDPRESS_VERIFY_DATABASE_SSL` | Whether to verify the database SSL certificate when SSL is enabled for database connections. | `yes` |\n| `WORDPRESS_DATABASE_SSL_CERT_FILE` | Path to the database client certificate file. | `nil` |\n| `WORDPRESS_DATABASE_SSL_KEY_FILE` | Path to the database client certificate key file. | `nil` |\n| `WORDPRESS_DATABASE_SSL_CA_FILE` | Path to the database server CA bundle file. | `nil` |\n| `WORDPRESS_OVERRIDE_DATABASE_SETTINGS` | Override the database settings in persistence. | `no` |\n\n#### Read-only environment variables\n\n| Name | Description | Value |\n|-----------------------------------|------------------------------------------------------|---------------------------------------|\n| `WORDPRESS_BASE_DIR` | WordPress installation directory. | `${BITNAMI_ROOT_\n\n_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_","has_starred","hub_user","immutable_tags_settings",{"_111":11,"_112":113},"enabled","rules",[114],".*","is_automated","permissions",{"_118":21,"_119":11,"_120":11},"read","write","admin","user","storage_size",684969926820,"isOrg","reponame","tag","canDeleteTags","isHubSbxKitsEnabled","currentTab","","tagAttestations","displaySecurityMetadata","showSbxLogoOverride","showSbxAgenticPlatformBadge","routes/_layout.layers.$namespace.$reponame.$tag.(images).($imageUrlDigest)._index",{"_26":27,"_62":-7,"_60":-7,"_61":-7,"_28":137,"_34":35,"_139":-7,"_140":11},{"_30":31,"_32":33,"_34":35,"_36":37,"_38":39,"_40":138,"_42":43,"_44":33,"_45":46,"_47":48,"_49":50,"_51":52,"_53":-5,"_54":43,"_55":56,"_57":21},[],"imageWithLayers","hasPermissionToViewRepoSettings","actionData","errors"]

bitnami/wordpress:sha256-4b1c708beb68ebff5382c0d4a21c2cb0c12fd3f1bdfcfe8a3c612629a655cfac.sig