Wordpress in Docker

[technorabilia]

Let's start with the containers logs. You can put it on pastebin or sprunge.us or a similar site.

 

[buckland]

I went through the logs and did a screen shot to jpg of the possible port error.... if this is so... I need to find an appropriate port #. I took the port # from the link page... hmmmm

 

[technorabilia]

WordPress cannot start because the MariaDB container where the WordPress database resides has stopped. Like you described a couple of posts back. So you need to get the logs of that container to see what happened to it.

 

[buckland]

Saved file as a pdf... hope this is okay.

 

[technorabilia]

The last log entry (at the top) gives you the answer. You need to specify the database root password.

Similar to this example.

WordPress samples

Docker samples for WordPress.

docs.docker.com

You need to specify this as an environment variable.

 

[Rusty]

Saved file as a pdf... hope this is okay.

How is your Maria container configured?

 

[buckland]

Will go through this tomorrow... thank you for your help. It is a new language to me and I move slow.

 

[technorabilia]

No problem!

I'm using docker-compose and probably confused you with it. Sorry about that.

I now see you probably followed this excellent guide here and use the Synology Docker GUI.

Set up wordpress on Synology using docker containers

Synology offers both MariaDB and Wordpress via the package center, but for those looking for a docker based solution this guide is intended to help.

ten20four.co.uk

Because of the error message you get (see PDF), I think you probably did not set the correct environment variables on the wordpress and wordpressdb containers.

From step #5 in the tutorial

MYSQL_DATABASE: name_your_database
MYSQL_ROOT_PASSWORD: choose_root_password
MYSQL_USER: your_user_name
MYSQL_PASSWORD: choose_user_password

Here you setup the WordPress database and user. You also specify a password for the root user (the administrator user for MariaDB).

MariaDB is a community-developed, commercially supported fork of the MySQL. That is why you see the MySQL prefixes...

Example

MYSQL_DATABASE: blog_db
MYSQL_ROOT_PASSWORD: root123
MYSQL_USER: wpuser
MYSQL_PASSWORD: wpuser123

From step #10

WORDPRESS_DB_HOST: the_container_name_for_your_DB (from step #1)
WORDPRESS_DB_NAME: name_of_your_database (from step #5)
WORDPRESS_DB_USER: user_name (from step #5)
WORDPRESS_DB_PASSWORD: user_password (from step #5)

Here you instruct WordPress to connect to the WordPress database that you setup earlier. With the same credentials from earlier: database name, user and password.

Example

WORDPRESS_DB_HOST: wordpressdb
WORDPRESS_DB_NAME: blogdb
WORDPRESS_DB_USER: wpuser
WORDPRESS_DB_PASSWORD: wpuser123

Then restart your containers.

 

[buckland]

I went in this morning and set up what was suggested above.... that said I appear to be missing applying my root password somewhere as when I turn on the container the db starts and then quits with the log saying (below photo):

 

[technorabilia]

Can you post the settings for both the wordpress and wordpressdb container?

DSM, Docker, Containers, <select the container>, Settings, Export, Export container settings.

 

[buckland]

I saved there .json files as pdf's

 

[technorabilia]

You should drop the ":" at the end of the variable name...

It is "MYSQL_ROOT_PASSWORD" and not "MYSQL_ROOT_PASSWORD:" (notice the ":" at the end).

Same goes for all the other variables.

 

[buckland]

For the love of Pete! Thanks. I'll go see what happens!

-- post merged: 5. Jun 2021 --

Well the did work! Thank you. Now just one more glitch. When I ...In General Settings, set up a Web Page shortcut for the desktop by using the local port #, I get an Error message saying "Error in making a Database connection"........ Should the Local Port number be the same as the Container Port number?

 

[technorabilia]

Not sure what you mean? You should now be able to access WordPress by pointing your browser to http://ip-address-nas:32789.

Edit:
Host and container port do not have to be the same. On the left you see the host port. On the right the container port. Do not change the container port.

Edit 2:
...and your WORDPRESS_DB_HOST should be wordpressdb and not wordpress.

 

[buckland]

Can't access via the ......:32789 . The local port in the Wordpress is 32789 The local port in the wordpressdb is "auto"

 

[technorabilia]

You shouldn't use auto. Set it to a port that is free and you like to use like e.g. 8080.

For example 8080:80 means port 8080 on the host maps to port 80 in the container and you can access the container through http://ip-address-nas:8080.

And you have the wrong WORDPRESS_DB_HOST setting. It should be wordpressdb and not wordpress. That is why the database connection fails.

 

[buckland]

I believe I am more confused than not. I did the WORD_DB_HOST setting change. I tried to change to local port at 8080 but it says I can't use as 8080 is already in use. So as you can tell I am a feck-all novice.. below is currently the two screen shots of the wordpress ports settings and the wordpressdb ports settings
Thanks for your patience

 

[technorabilia]

Maybe it is best if you check the guide once more?

From the guide:

#3. Maria - Port Settings
Since we will be using names, you can leave this tab as Auto.

So this will look like Auto:3306.

#8. Wordpress - Port Settings
Since you will want to be able to access your Wordpress site from the web, you will need to specify a port to connect to port 80 on the container.

If port 8080 is already in use you can use another port like 8888.

So this will look like 8888:80.

WordPress will be available on http://ip-address-nas:8888.

 

[buckland]

Can't thank you enough for you perseverance with my limited patchwork knowledge. It actually works! I am chipping away at the mountain. Now I will start learning up on moving my travel blog over. I had it in google blog when i was traveling, then recently moved it to WP on the NAS. I thought it better to learn how to use Docker before I invest in putting time into 3rd party programs on the NAS. Docker seems to be what makes more sense. Again thanks for your guidance.

 

[technorabilia]

Alright!

No problem, happy to help.

The beginning is always the hardest, but you will get the hang of it. You'll see...