It's not clear how to support HTTPS with this image.

Ideally one could provide something like PORT for the Apache server to listen on, plus a KEY and CERT environment variables with the contents of the key and cert files.

I can try and make this work.

Right now you can browse the /wp-content/uploads directory of a site deployed from this image.

I've fixed this by adding the following line to each of my derived images:

RUN sed -i 's/Indexes //g' /etc/apache2/apache2.conf

I'm sure there's a less dangerous way of doing the above, but I'm thinking that disabling indexes should be the default behavior. Thoughts?

When I stop and restart my wordpress container, it gets a new IP. When I access the service at the new IP, the page is malformed because it has hardcoded refs to the old IP.

Am I doing something wrong or is this image reliant on non-changing IPs?

All is in the title. Any ideas ?

Would it be possible to add this option in the Dockerfile ?

Try to run a container with

docker run --name mysql -e MYSQL_ROOT_PASSWORD=vetslist -d mysql:5.7

docker run --name wordpress -e WORDPRESS_DB_PASSWORD=vetslist -e WORDPRESS_DB_USER=root -e WORDPRESS_DB_HOST=localhost -e WORDPRESS_DB_NAME=wordpress --link mysql:mysql-server -p 8080:80 -d wordpress

Keeps failing with
osxlthbrien:VetsList hbrien$ docker logs wordpress
WordPress not found in /var/www/html - copying now...
Complete! WordPress has been successfully copied to /var/www/html

Warning: mysqli::mysqli(): (HY000/2002): No such file or directory in - on line 10

MySQL Connection Error: (2002) No such file or directory

Warning: mysqli::mysqli(): (HY000/2002): No such file or directory in - on line 10

MySQL Connection Error: (2002) No such file or directory

Warning: mysqli::mysqli(): (HY000/2002): No such file or directory in - on line 10

MySQL Connection Error: (2002) No such file or directory

Hi,
I am using official mysql container as DB and after pulling the "latest", I am starting it with:
docker run --name somename-mysql -e MYSQL_ROOT_PASSWORD=somepass -d mysql

Then I start latest wordpress container:
docker run --name somename-wordpress --link somename-mysql:mysql -p 8080:80 -d wordpress

I have added some content to wordpress page.

I regularly backup both containers with the following commands:
docker commit mysql:sometag
docker commit wordpress:sometag
docker save wordpress:sometag | gzip > wordpress.tar.gz
docker save mysql:sometag | gzip > mysql.tar.gz

After moving the tar.gz files into another docker host and loading them:
docker load < mysql.tar.gz
docker load < wordpress.tar.gz

I cannot see the repo name and tag. Therefore I have to start the containers with the above run parameters using corresponding image IDs. But after this operation I cannot see the content. I only get wordpress' installation screen. Do I something wrong?

Any help will be appreciated. Have a nice day.

I am trying to run official wp image with official mysql image and it fails to start with following error.

$ sudo fig up
Creating wordpressdocker_mysql_1...
Creating wordpressdocker_wordpress_1...
Attaching to wordpressdocker_mysql_1, wordpressdocker_wordpress_1
mysql_1     | 2014-10-31 00:57:15 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
mysql_1     | 2014-10-31 00:57:15 13 [Note] InnoDB: Using atomics to ref count buffer pool pages
mysql_1     | 2014-10-31 00:57:15 13 [Note] InnoDB: The InnoDB memory heap is disabled
mysql_1     | 2014-10-31 00:57:15 13 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
mysql_1     | 2014-10-31 00:57:15 13 [Note] InnoDB: Memory barrier is not used
mysql_1     | 2014-10-31 00:57:15 13 [Note] InnoDB: Compressed tables use zlib 1.2.3
mysql_1     | 2014-10-31 00:57:15 13 [Note] InnoDB: Using Linux native AIO
mysql_1     | 2014-10-31 00:57:15 13 [Note] InnoDB: Not using CPU crc32 instructions
mysql_1     | 2014-10-31 00:57:15 13 [Note] InnoDB: Initializing buffer pool, size = 128.0M
mysql_1     | 2014-10-31 00:57:15 13 [Note] InnoDB: Completed initialization of buffer pool
mysql_1     | 2014-10-31 00:57:15 13 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!
mysql_1     | 2014-10-31 00:57:15 13 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB
mysql_1     | 2014-10-31 00:57:15 13 [Note] InnoDB: Database physically writes the file full: wait...
mysql_1     | 2014-10-31 00:57:16 13 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB
mysql_1     | 2014-10-31 00:57:20 13 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB
mysql_1     | 2014-10-31 00:57:24 13 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
mysql_1     | 2014-10-31 00:57:24 13 [Warning] InnoDB: New log files created, LSN=45781
mysql_1     | 2014-10-31 00:57:24 13 [Note] InnoDB: Doublewrite buffer not found: creating new
mysql_1     | 2014-10-31 00:57:24 13 [Note] InnoDB: Doublewrite buffer created
mysql_1     | 2014-10-31 00:57:24 13 [Note] InnoDB: 128 rollback segment(s) are active.
mysql_1     | 2014-10-31 00:57:24 13 [Warning] InnoDB: Creating foreign key constraint system tables.
wordpress_1 | WordPress not found in /var/www/html - copying now...
mysql_1     | 2014-10-31 00:57:25 13 [Note] InnoDB: Foreign key constraint system tables created
mysql_1     | 2014-10-31 00:57:25 13 [Note] InnoDB: Creating tablespace and datafile system tables.
mysql_1     | 2014-10-31 00:57:25 13 [Note] InnoDB: Tablespace and datafile system tables created.
mysql_1     | 2014-10-31 00:57:25 13 [Note] InnoDB: Waiting for purge to start
mysql_1     | 2014-10-31 00:57:25 13 [Note] InnoDB: 5.6.21 started; log sequence number 0
wordpress_1 | Complete! WordPress has been successfully copied to /var/www/html
wordpress_1 | PHP Warning:  mysqli::mysqli(): (HY000/2003): Can't connect to MySQL server on '172.17.0.16' (111) in - on line 5
wordpress_1 | MySQL Connection Error: (2003) Can't connect to MySQL server on '172.17.0.16' (111)
wordpressdocker_wordpress_1 exited with code 1
Gracefully stopping... (press Ctrl+C again to force)
Stopping wordpressdocker_mysql_1...
$

fig.yml looks like

wordpress:
  image: wordpress
  links:
    - mysql:mysql
  ports:
    - "80:80"

mysql:
  image: mysql
  ports:
    - 3306
  environment:
    MYSQL_ROOT_PASSWORD: mysecretpassword
    MYSQL_DATABASE: wordpress

additional information

# docker info
Containers: 2
Images: 118
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Dirs: 124
Execution Driver: native-0.2
Kernel Version: 3.16.3-1-aufs_friendly
Operating System: Arch Linux
WARNING: No swap limit support

# docker version
Client version: 1.3.0
Client API version: 1.15
Go version (client): go1.3.3
Git commit (client): c78088f
OS/Arch (client): linux/amd64
Server version: 1.3.0
Server API version: 1.15
Go version (server): go1.3.3
Git commit (server): c78088f

Similar error was replicated with with another system running ubuntu:14.04.

Can we look at it and determine what's causing this?

Here is the output from the docker logs:

Complete! WordPress has been successfully copied to /var/www/html
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.4. Set the 'ServerName' directive globally to suppress this message
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.4. Set the 'ServerName' directive globally to suppress this message
[Thu Mar 12 20:44:12.294365 2015] [mpm_prefork:notice] [pid 1] AH00163: Apache/2.4.10 (Debian) PHP/5.6.6 configured -- resuming normal operations
[Thu Mar 12 20:44:12.294449 2015] [core:notice] [pid 1] AH00094: Command line: 'apache2 -D FOREGROUND'

When I try and reach the container I get nothing back. I'm guessing the server isn't serving on the correct IP for public traffic - what is the correct method to modify this?

Appreciate the help.

Hi all,
I created a docker-compose file to make the images work taking an existing wordpress folder that is on my home.
Here is the docker-compose.yml

wordpress:
  image: wordpress
  links:
    - db:mysql
  ports:
    - 8082:80
  environment:
    WORDPRESS_DB_USER: test
    WORDPRESS_DB_PASSWORD: test
    WORDPRESS_DB_NAME: test
  volumes:
     - /home/tubia/test/:/var/www/html

db:
  image: mysql
  environment:
    MYSQL_ROOT_PASSWORD: example
    MYSQL_DATABASE: test
    MYSQL_USER: test
    MYSQL_PASSWORD: test

This results in the installation page, when I visit localhost:8082, so it is not taking the volume as configured. Also If I enter the container with docker exec -ti wp_container /bin/bash and ls the /var/www/html, it's a standard default wp installation, not the one I mapped with the volume.

Hints? It is the expected behaviour?

If you're going to run on docker, the last thing you should be concerned with is too big files being uploaded.

As it turns out, JPEG support is missing in GD. This means that you cannot use the bult-in image editor for anything but PNG files.

here's from PHP.

$ php -i 
[...]
gd

GD Support => enabled
GD Version => bundled (2.1.0 compatible)
GIF Read Support => enabled
GIF Create Support => enabled
PNG Support => enabled
libPNG Version => 1.2.50
WBMP Support => enabled
XBM Support => enabled

Directive => Local Value => Master Value
gd.jpeg_ignore_warning => 0 => 0
[...]

As is event above, JPEG support is absent.

Can be pre-configured FTP server for wordpress container/image?

I know this is a mariadb issue but nontheless the docker compose file doesn't seem to work because by default MariaDB container doesn't allow remote connections:

Warning: mysqli::mysqli(): (HY000/1130): Host '172.17.0.19' is not allowed to connect to this MariaDB server in - on line 10

I've only gotten this since today when i pulled the latest mariadb image.

This may not be supported but none the less. I have boot2docker 1.4.1 installed on OS X Yosemite. I also have fig 1.0.1 installed.

It looks like the WordPress image makes the assumption that the link to mysql is available at the time the container loads and exits immediately with a failure if it isn't. I assume the mysql client is attempting to setup the databases for first launch to save the user the trouble from doing this, however this makes the assumption the service/application has already been started when in reality WordPress itself doesn't require the database created for 'installation'. It is required for 'configuration' and 'usage', both steps that could be done once the connection to the db is established (at any time). At the very least the container could make use of the mysqli.reconnect to reestablish the connection when lost.

Steps to reproduce:

0. Create a fig.yml containing:

db:
  image: mysql:latest
  ports:
    - "3306"
  environment:
    - MYSQL_ROOT_PASSWORD=wordpress
    - MYSQL_PORT_3306_TCP=3306
web:
  image: wordpress:latest
  ports:
    - "8080:80"
  links:
    - db:mysql
  environment:
    - WORDPRESS_DB_USER=root
    - WORDPRESS_DB_PASSWORD=wordpress
    - WORDPRESS_DB_NAME=wordpress
  expose:
    - "8080"

1. Verify no containers are running:

$ fig ps
Name   Command   State   Ports 
------------------------------

2. Start up the containers (in a detached mode)

$ fig up -d
Creating example_db_1...
Creating example_web_1...

3. List the containers

$ fig ps
       Name                      Command               State             Ports          
---------------------------------------------------------------------------------------
example_db_1    /entrypoint.sh mysqld            Up       0.0.0.0:49183->3306/tcp 
example_web_1   /entrypoint.sh apache2-for ...   Exit 1 

4. Looking at the logs

$ fig logs
Attaching to example_web_1, example_db_1
web_1 | WordPress not found in /var/www/html - copying now...
web_1 | Complete! WordPress has been successfully copied to /var/www/html
web_1 | 
web_1 | Warning: mysqli::mysqli(): (HY000/2002): Connection refused in - on line 5
web_1 | MySQL Connection Error: (2002) Connection refused
db_1  | Running mysql_install_db ...

5. Relaunch the containers

fig up -d
Recreating example_db_1...
Recreating example_web_1...

6. Check the processes

$fig ps
       Name                      Command               State               Ports              
---------------------------------------------------------------------------------------------
example_db_1    /entrypoint.sh mysqld            Up      0.0.0.0:49184->3306/tcp        
example_web_1   /entrypoint.sh apache2-for ...   Up      0.0.0.0:8080->80/tcp, 8080/tcp 

Hi guys I'm quite new to Docker and I've been getting this error when trying to activate WPML plugin, any way around this?

Fatal error: Call to undefined function mb_strtolower() in /var/www/html/wp-content/plugins/sitepress-multilingual-cms/inc/sitepress-schema.php on line 464

Not sure if there is something I need to enable in .htaccess or this module is not compiled at all?

Any thoughts regarding HHVM support?

$ docker run -e WORDPRESS_DB_HOST=10.1.2.3:3306 -e WORDPRESS_DB_USER=root -e WORDPRESS_DB_PASSWORD=foobarzoo wordpress
docker run -e WORDPRESS_DB_HOST=10.1.2.3:3306 -e WORDPRESS_DB_USER=root -e WORDPRESS_DB_PASSWORD=foobarzoo wordpress
WordPress not found in /var/www/html - copying now...
Complete! WordPress has been successfully copied to /var/www/html
^C^[[A^C^C^C^C


^C
^C
^C^Z^Z
^Z^Z^Z^C^C^C^C^C^Z^C^Z^C^Z^C^Z
^C^C^Z^C^Z
^C
^C
^C^C
^C
^C^Z^Z^C^Z
^Z
^C^Z

Warning: mysqli::mysqli(): (HY000/2002): Connection timed out in - on line 10

MySQL Connection Error: (2002) Connection timed out
^C^C
^C^Z^Z^C^C^Z^C^Z

I got trapped in the command prompt.

Hi,

I am having trouble with Nginx configuration to proxy a sub-directory to my wordpress:fpm container in Docker on CoreOS. I have combined information from Nginx's website as well as gist by @md5 to come up with the following without success:

upstream wordpress {
        server 172.17.42.1:3001;
}

server {
        listen 80;
        server_name sub.domain.com;
        root /var/www/html;
        index index.php;

        location /subdirectory {
                proxy_pass http://wordpress;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_set_header X-NginX-Proxy true;
                proxy_set_header Host $host;
                try_files $uri $uri/ /subdirectory/index.php?$args;
        }

        rewrite /wp-admin$ $scheme://$host$uri/ permanent;

        location ~ [^/]\.php(/|$) {
                fastcgi_split_path_info ^(/subdirectory)(/.*)$;
                if (!-f $document_root$fastcgi_script_name) {
                        return 404;
                }
                include fastcgi_params;
                fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
                fastcgi_param PATH_INFO $fastcgi_path_info;
                fastcgi_param PATH_TRANSLATED $document_root$fastcgi_path_info;
                #fastcgi_pass fpm:9000;
                fastcgi_index index.php;
        }
}

I had to comment fastcgi_pass fpm:9000; to prevent Nginx from crashing. I am running my container as such:

docker run --name="wordpress" --restart="always" --link mariadb:mysql -e WORDPRESS_DB_NAME=wpdb -p 3001:80 -d wordpress:fpm

Nginx container performing the proxy for all my sub-directories is run as follows:

docker run --name="nginx" -v /home/core/custom.conf:/etc/nginx/conf.d/custom.conf:ro -p 80:80 nginx:latest

Thank you.

Warmest Regards,
Joel

Hi,
I've run this image on two different machines, but encountered the same issue on both. Everything appears to work fine, but the wordpress admin pages respond very slowly and display this error at the top:
"Warning: An unexpected error occurred. Something may be wrong with WordPress.org or this server’s configuration. If you continue to have problems, please try the support forums. (WordPress could not establish a secure connection to WordPress.org. Please contact your server administrator.) in /var/www/html/wp-includes/update.php on line 295"
It appears to be struggling to contact api.wordpress.org. I've checked from the container that I can curl the API, and the install seems to work - I installed a couple of plugins, for instance. I've tried turning on PHP logging and tracing through the update code, but I can't see anything out of the ordinary.
I'm running docker v1.4 in an ubuntu VM via vagrant, on a linux mint host. Wordpress is accessed via an nginx reverse proxy, but in the other instance I set up I accessed wordpress direct (not via nginx proxy).
It looks like a DNS or proxy issue, or that something is timing out, but as I say other connectivity on the instance appears fine. Any ideas?

mysql instance running at 172.17.0.2

# docker run -ti --rm --link wordpress-mysql:mysql busybox ping "mysql"
PING mysql (172.17.0.2): 56 data bytes
64 bytes from 172.17.0.2: seq=0 ttl=64 time=3.477 ms
64 bytes from 172.17.0.2: seq=1 ttl=64 time=0.061 ms

because previous version, wordpress container cannot be start again see #38 . so I have to start a new container of wordpress. but newly created container always exits immediately after creation. and I observed that mysql host ip is increasing automatically.

# docker run --link wordpress-mysql:mysql --volumes-from wordpressData -p 80:80 -e WORDPRESS_DB_PASSWORD='$MYSQL_ROOT_PASSWORD' -ti --rm  wordpress /bin/sh

Warning: mysqli::mysqli(): (HY000/1045): Access denied for user 'root'@'172.17.0.17' (using password: YES) in - on line 5
MySQL Connection Error: (1045) Access denied for user 'root'@'172.17.0.17' (using password: YES)
# docker run --link wordpress-mysql:mysql --volumes-from wordpressData -p 80:80 -e WORDPRESS_DB_PASSWORD='$MYSQL_ROOT_PASSWORD' -ti --rm  wordpress /bin/sh

Warning: mysqli::mysqli(): (HY000/1045): Access denied for user 'root'@'172.17.0.18' (using password: YES) in - on line 5
MySQL Connection Error: (1045) Access denied for user 'root'@'172.17.0.18' (using password: YES)

I didn't observe the same behavior of other images.

# docker run -ti --rm --link wordpress-mysql:mysql busybox ping -c 2 "mysql" && date
PING mysql (172.17.0.2): 56 data bytes
64 bytes from 172.17.0.2: seq=0 ttl=64 time=0.774 ms
64 bytes from 172.17.0.2: seq=1 ttl=64 time=0.062 ms

--- mysql ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 0.062/0.418/0.774 ms
Fri Jan 16 06:17:43 UTC 2015
# docker run -ti --rm --link wordpress-mysql:mysql busybox ping -c 2 "mysql" && date
PING mysql (172.17.0.2): 56 data bytes
64 bytes from 172.17.0.2: seq=0 ttl=64 time=0.648 ms
64 bytes from 172.17.0.2: seq=1 ttl=64 time=0.081 ms

--- mysql ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 0.081/0.364/0.648 ms
Fri Jan 16 06:17:46 UTC 2015

restart host machine, start wordpress_mysql ok. but when to start / restart wordpress container directly. log says:

 $ docker start 84c63ccfcde0
 $ docker logs --tail=10 

  ...
 httpd (pid 1) already running

docker process

84c63ccfcde0        wordpress:4                 "/entrypoint.sh apac   27 hours ago        Exited (0) 22 seconds ago                       wordpress           
6bdd37b885fa        mysql:5                     "/entrypoint.sh mysq   27 hours ago        Up 3 minutes                3306/tcp            wordpress-mysql  

Hi,

Yesterday I've been trying to setup WPML and found that it is "broken" and couldn't finish the setup. It turned out that the plugin relies on $_SERVER[ 'HTTP_HOST' ] and in my case instead of 192.168.59.103 it returns "wordpress" which breaks the functionality.

Is there a way other than hardcoding it in wp-config.php to pass the IP, or there is some other solution. I'm using fig.

Thanks,
Marko

I am trying to install some php plugins following the tutorial on the main page for wp-fpm.

here is my example
RUN apt-get update && apt-get install -y \ libfreetype6-dev \ libjpeg62-turbo-dev \ libmcrypt-dev \ libpng12-dev \ libzip-dev \ && docker-php-ext-install iconv mcrypt zip

For the plugins the grep is incorrect grep: /usr/local/etc/php/conf.d/docker-php-ext-iconv.ini the correct path however would be grep: /usr/local/etc/php/conf.d/ext-iconv.ini

Installing shared extensions:     /usr/local/lib/php/extensions/no-debug-non-zts-20131226/
Installing header files:          /usr/local/include/php/
grep: /usr/local/etc/php/conf.d/docker-php-ext-iconv.ini: No such file or directory
find . -name \*.gcno -o -name \*.gcda | xargs rm -f
find . -name \*.lo -o -name \*.o | xargs rm -f
find . -name \*.la -o -name \*.a | xargs rm -f 
find . -name \*.so | xargs rm -f
find . -name .libs -a -type d|xargs rm -rf
rm -f libphp.la       modules/* libs/*
+ cd /usr/src/php/ext/mcrypt
+ phpize

Is there a workaround or can this error be ignored.

made an issue here by mistake. please delete.

As it currently stands, anything in Wordpress that needs to send email is broken. The wp_mail function that is used for sending out email by default is a thin wrapper over PHP's mail function, which defaults to calling /usr/sbin/sendmail -t -i (cf. http://php.net/manual/en/mail.configuration.php). There are php.ini settings for SMTP, but they are only used on Windows.

For my own work based on this image, I've been installing ssmtp and configuring it to use an external relay host for SMTP, but that's clearly not a turnkey solution for everyone. It also looks like there are many Wordpress plugins that provide SMTP support, but I don't think that installing any of them by default in this image seems reasonable.

Perhaps all of this should just be documented, but I wanted to get it on your radar.

I'm trying to build a container derived from the wordpress image with my themes and plugins already in place. This works fine when starting from a fresh volume but after it's installed no updates I push to the /usr/src/wordpress takes effect.

looking at the entrypoint script this seems to be intentional but it would be nice to have a way of bypassing the already installed check and always rsync (or tar).

The entrypoint for this image unconditionally updates the wp-config.php file with values from the environment, at least in the common case that the value in the config file is a simple single- or double-quoted string. This may not be desirable in all circumstances; for example, I think the changes to the *_KEY and *_SALT values may cause logged-in cookies to be invalidated after a container restart.

I'm not a fan of introducing extra magic environment variables, but it would be nice to have a way to skip this behavior while still using wordpress as a base image.

It would make sense to move this to running on Nginx + PHP-FPM as not only would it be faster, scale better but also result in a smaller Docker image.

If mysql and wordpress is started with --restart=always I would expect that after hosts system reboot Wordpress will come up clearly. This dosn't work.

I think that problem is in how config file is generated. After reboot mysql has different IP and this is not reflected in the wp-config.php.

Hey, how can i use this image to install wordpress 3.8.* instead of the latest one ?

I ran into an issue with the image cropping not working for certain files. No way to get PHP errors back, so no idea if there's a missing library. Need a way to set error login to max in php.ini and/or wpconfig.php

The wordpress tarball is currently being downloaded over http without any checksum testing.

In short, this means the image could be downloading anything, including malicious software, and end users are blindly trusting this software with their data. IMO official images should be more careful about this (and most of them are).

Currently, the Dockerfile references 4.2.1

My pull request was merged 2 days ago, but https://registry.hub.docker.com/_/wordpress/ is still showing the previous version.

I am using the current latest wordpress container, and when I try to crop image inside Media library, I get an error message

"There has been an error cropping your image".

Is it reported here

http://terminaltwister.com/there-has-been-an-error-cropping-your-image-solution-to-wordpress-error/

that you need to install php-gd.

I'm not sure whether this is for the wordpress image or its parent image, but some of the wordpress plugins do require mcrypt. So what is the basic process of adding such libraries? Obviously I could create a personal image, but I would prefer to stay with the official image. On the other hand side I guess with all kinds of different libraries the images will get too large. Is there any definition what goes inside the official images and what stays out?
Thanks!

not sure what your feelings are about this, but it would be handy to have this exposed.

1. wp-content/uploads is where images and other user-uploaded content gets put, so you need a way to back it up
2. it allows people to easily add/update themes/plugins

Hi All,

I have successfully created/tested dockerfile for wordpress on power architecture(ppc64le) - on Ubuntu 14.10 (using single container approach using supervisor - reference : https://github.com/how2dock/docbook/tree/master/ch01/supervisor) /Rhel 7.1 ( Using two container approach - Apache/mysql ) .

Could you please let me know the steps of contributing the dockerfile (not the docker container ) for wordpress on ppc64le architecture at this location .?

Regards,
Amit

Since this image has been changed to be based on php:apache, the $APACHE_* environment variables are no longer used/available. Yet they're still used in a chown call in the entrypoint (cf. https://github.com/docker-library/wordpress/blob/master/docker-entrypoint.sh#L117). The actual chown call ends up being chown -R ":" ..

I can provide a PR that either removes this or updates it to be chown -R www-data: ..

From my AWS instance, when I run:
sudo docker pull wordpress:latest

I get:

downloads... downloads.. downloads
69387ad66963: Download complete
6e0782896a9b: Error downloading dependent layers
2015/01/21 02:14:20 Could not find repository on any of the indexed registries.

i want use to Active Directory Integration Plugin.

but, show the following at plugin setting page.
same even if installed php5-ldap module.
please help

 ATTENTION: You have no LDAP support. This plugin won´t work.

You must install or enable LDAP support in PHP. Further information: http://php.net/manual/en/book.ldap.php at the pluginsetting page 

I don't know why this is happening, as on my dev box (ubuntu 14.04/docker1.1.2) it works as advertised.
but on my staging server (centos 6.5/docker 1.0.0) the file 'index.html' isn't removed

I'm using the latest official mysql and wordpress images with boot2docker on my Mac. They are started in normal way. When I use the wordpress image to start a container without mount-bind /var/www/html/ to any other container or host directory everything works as expected. During startup of the wordpress container a wordpress installation is done and when I access the page the first time I do see install screen with the language selection.
However, as soon as I do mount-bind the /var/www/html/ directory to an empty host dir (e.g. -v $(pwd):/var/www/html/ ), I do get the install screen, but without the language selection.
It seems that in both cases the wordpress instance works fine, but I would like to have it not in English.

Any thoughts?

Jan

During development I mount /var/www/html to my host. I dont have permissions in there to change/add/delete files.

Enable option to install wordpress networks (wordpress multiuser)

In the AWS blog post for ElasticBeanstalk with docker Jeff Barr explains several environment variables are exposed:

• RDS_DB_NAME
• RDS_USERNAME
• RDS_PASSWORD
• RDS_HOSTNAME

I know it's a long shot, but support for these would be great. Otherwise I'll end up making my own image

I am evaluating the deployment of wordpress with docker for high availability and the biggest issue I found so far is wordpress need for a persisted file system (for uploads/themes etc). This is not particularly docker related, but as docker containers are ephemeral, there should be some tips and tricks to work around this.

So far, I have seen two approaches, a stateful and stateless one. As the stateless version fits better to the docker principles, you have to tweak wordpress very much and the configuration is not very comfortable. The stateful version doesn't need modifications to wordpress but have deal with a distributed filesystem.

At the moment, I would start with the stateless approach, because running distributed filesystems in a docker cluster doesn't seem to be an easy task.

I appreciate any ideas, experiences to this topic. Thanks.

I've been trying to connect this image to a non-docker mysql server for the better part of a day. I was able to do it with 3.9, however anything above that doesn't seem to work. There's no documentation either, which has made life hell.

It's be great if we could:

• Document the procedure of connecting to an external mysql database and
• Look into why it doesn't work on versions after 3.9