1

Hi all. I used this method which worked just fine:

I am on Ubuntu 22.04 and had no errors when doing this process. After I spin up the docker container, everything that was (is) on the existing hardware 12.04 lamp server is on the container, so all good.

My question from this point: When I try to access the website on the now running container, nothing shows up at all - Generic web error of ‘site cannot be reached’. I have the correct ports mapped from host to container etc. I am guessing there may be some config that needs to be changed but I am not sure which if any.

Can anyone shed some light or have a link that I can look at to progress?

Ideally, I want to get my aging website off my aging hardware into a docker container while I rebuild my website in the event there is any failure.

Thanks in advance.

6 Spice ups
2

From your client machine, can you ping the web server or the OS within the container ?

How are you publishing the website ??

Your aging hardware website might be publish via the DMZ etc

3

Hi

Just for some context, the existing old hardware is VMWare Virtual Machine (hence why I exported it and converted it)

I am hosting the new docker container on a dedicated 22.04 Ubuntu server which I can definately ping & access via ssh etc. The internal IP of the container I cannot ping. However, from within the container, I can ping my machine and my local network.

4

Probably you cannot ping the container 'cause there is no route to it, or docker is blocking access for other ports that aren’t published. Normal. use telnet or curl to access your containerized web server, directioning the command to the container host itself - it’s a published port, isn’t it? In some circumstances you can ping the host by name -as the host can change its IP address when restarted.

I have a similar setup here, the main difference is the web server - apache2 - runs on a VM, and mariadb, redis, phpmyadmin - all are containers. Have set this up there is near a year ago, no issues whatsoever.

You’ll need to publish ports 80 and 443 to get a valid cert. That’s why I found easier to set up a VM as a webserver: I can DNAT requests to these ports, MASQ them and all goes well.

HTH,