{"id":3148,"date":"2019-10-22T22:16:10","date_gmt":"2019-10-23T03:16:10","guid":{"rendered":"http:\/\/osric.com\/chris\/accidental-developer\/?p=3148"},"modified":"2019-10-27T18:15:00","modified_gmt":"2019-10-27T23:15:00","slug":"running-joomla-on-docker","status":"publish","type":"post","link":"https:\/\/osric.com\/chris\/accidental-developer\/2019\/10\/running-joomla-on-docker\/","title":{"rendered":"Running Joomla on Docker"},"content":{"rendered":"

I was looking for a well-known CMS (Content Management System) that I could easily run in a Docker container as a target for information security reconnaissance tools, such as WhatWeb<\/a>.<\/p>\n

I found an official Docker image for Joomla<\/a>, a CMS that I had used previously some years ago: https:\/\/hub.docker.com\/_\/joomla<\/a>
\n<\/p>\n

Using a backend MySQL database on localhost<\/strong><\/p>\n

I had some problems running it at first. I tried to set up a local MariaDB\/MySQL database and have the Joomla container communicate directly with the underlying host:<\/p>\n

docker run --name some-joomla -e JOOMLA_DB_HOST=localhost:3306 -e JOOMLA_DB_USER=joomla -e JOOMLA_DB_PASSWORD=joomP455 -d joomla<\/code><\/pre>\n
That didn’t work. The Joomla container crashed shortly after starting. When I looked at the container logs using the following command:<\/p>\n
docker logs some-joomla<\/code><\/pre>\n
I found the same error message repeated several times:<\/p>\n
Warning: mysqli::__construct(): (HY000\/1045): Access denied for user 'joomla'@'localhost' (using password: YES) in \/makedb.php on line 20<\/code><\/pre>\n
Of course! Within the context of the container, localhost<\/code> means the container itself!<\/p>\n
I was able to get this to work by specifying --network=host<\/code>. (See Use Host Networking<\/a> in the Docker documentation.)<\/p>\n
Here was the command I used (after creating a joomla database and joomla database user):<\/p>\n
docker run --name some-joomla -e JOOMLA_DB_HOST=127.0.0.1 -e JOOMLA_DB_USER=joomla -e JOOMLA_DB_PASSWORD=joomP455 -e JOOMLA_DB_NAME=joomla --network host -d joomla<\/code><\/pre>\n
Using a Dockerized MySQL database as the backend<\/strong><\/p>\n
That was great progress! But since this was just for a temporary demo, I found an even easier way: using a MySQL Docker container as the backend database: https:\/\/hub.docker.com\/_\/mysql<\/a><\/p>\n
This is what I tried the first time:<\/p>\n
docker run --name some-mysql -e MYSQL_ROOT_PASSWORD=passW0rd -e MYSQL_DATABASE=joomla -e MYSQL_USER=joomla -e MYSQL_PASSWORD=joomP455 -d mysql:latest<\/code><\/pre>\n
That didn’t work, though. When I started the Joomla container using the following command:<\/p>\n
docker run --name some-joomla --link some-mysql:mysql -p 8080:80 -d joomla:latest<\/code><\/pre>\n
The container would soon stop. I looked at the logs using docker logs some-joomla<\/code> and found the same error message repeated numerous times:<\/p>\n
Warning: mysqli::__construct(): The server requested authentication method unknown to the client [caching_sha2_password] in \/makedb.php on line 20<\/code><\/pre>\n
I searched for that error message, and found a GitHub issue for another project that suggested downgrading MySQL (https:\/\/github.com\/laradock\/laradock\/issues\/1390<\/a>).<\/p>\n
docker run --name some-mysql -e MYSQL_ROOT_PASSWORD=passW0rd -e MYSQL_DATABASE=joomla -e MYSQL_USER=joomla -e MYSQL_PASSWORD=joomP455 -d mysql:5\r\n\r\ndocker run --name some-joomla --link some-mysql:mysql -p 8080:80 -d joomla:latest<\/code><\/pre>\n
It worked! I was able to access the Joomla setup on http:\/\/localhost:8080<\/p>\n
However, I ran into an error on step 2 of the web-based Joomla setup (configuring the database):<\/p>\n
Error\r\nCould not connect to the database. Connector returned number: Could not connect to MySQL server.<\/code><\/pre>\n
I turns out, I had specified localhost<\/code> as the database host, as suggested. This is, of course, the same problem I had before: localhost<\/code>, on the container, is the container itself! I used the following command:<\/p>\n
docker inspect some-mysql<\/code><\/pre>\n
From that output I discovered that the some-mysql<\/code> container’s IP address was 172.17.0.2, which was reachable from the other container.<\/p>\n
Unless your Docker installation is substantially different, if you start the some-mysql<\/code> container followed by the some-joomla<\/code> container, you can likely used the same IP address I did. (In my case, the some-joomla container’s IP address was the next sequential address: 172.17.0.3.)<\/p>\n
Scanning the Joomla container<\/strong><\/p>\n
Now I had a running Joomla instance that I could target using WhatWeb and other scanners:<\/p>\n
# whatweb -a 4 localhost:8080\r\n\r\nhttp:\/\/localhost:8080 [200 OK] Apache[2.4.38], Cookies[e6b39c2ef305d5fa34c3ba66a227b8de], HTML5, HTTPServer[Debian Linux][Apache\/2.4.38 (Debian)], HttpOnly[e6b39c2ef305d5fa34c3ba66a227b8de], IP[::1], JQuery, MetaGenerator[Joomla! - Open Source Content Management], OpenSearch[http:\/\/localhost:8080\/index.php\/component\/search\/?layout=blog&amp;id=9&amp;Itemid=101&amp;format=opensearch], PHP[7.2.23], Script, Title[Home], X-Powered-By[PHP\/7.2.23]<\/code><\/pre>\n","protected":false},"excerpt":{"rendered":"
I was looking for a well-known CMS (Content Management System) that I could easily run in a Docker container as a target for information security reconnaissance tools, such as WhatWeb. I found an official Docker image for Joomla, a CMS that I had used previously some years ago: https:\/\/hub.docker.com\/_\/joomla<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[451,381],"tags":[449,543,36],"class_list":["post-3148","post","type-post","status-publish","format-standard","hentry","category-docker","category-mysql","tag-docker","tag-joomla","tag-mysql"],"_links":{"self":[{"href":"https:\/\/osric.com\/chris\/accidental-developer\/wp-json\/wp\/v2\/posts\/3148","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/osric.com\/chris\/accidental-developer\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/osric.com\/chris\/accidental-developer\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/osric.com\/chris\/accidental-developer\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/osric.com\/chris\/accidental-developer\/wp-json\/wp\/v2\/comments?post=3148"}],"version-history":[{"count":10,"href":"https:\/\/osric.com\/chris\/accidental-developer\/wp-json\/wp\/v2\/posts\/3148\/revisions"}],"predecessor-version":[{"id":3166,"href":"https:\/\/osric.com\/chris\/accidental-developer\/wp-json\/wp\/v2\/posts\/3148\/revisions\/3166"}],"wp:attachment":[{"href":"https:\/\/osric.com\/chris\/accidental-developer\/wp-json\/wp\/v2\/media?parent=3148"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/osric.com\/chris\/accidental-developer\/wp-json\/wp\/v2\/categories?post=3148"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/osric.com\/chris\/accidental-developer\/wp-json\/wp\/v2\/tags?post=3148"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}