#prod home route is redirected to some php Info default web page

[upgrader-dev]

Hello,

I have an existing project and followed the documentation regarding this case.

Everything works just fine in dev mode on my local machine.

When I deploy on my server in production mode I get no error but when I get to my server name, I am being redirected to some default php info Web page and never on my app.

Same error than here apparently :
https://stackoverflow.com/questions/77761841/symfony-ignores-routing-and-shows-phpinfo

I also tried to deploy the app on my server in dev mode but same issue.

Any idea?

[7-zete-7]

Hi @upgrader-dev!

It's hard to say what could be the reason based on the current information.

It looks like this is related to #632.

Will you be able to create a minimal reproducer of this issue? Or a sequence of actions that can lead to this error?

[upgrader-dev]

Hello @7-zete-7 Exact same issue you're right. But despite its status "Closed", I was unable to find a solution in this one #632

To create this issue I followed the same steps as the issue above.

[7-zete-7]

@upgrader-dev, can you try to build images and then restart the Docker Compose project and see if the problem persists?

I suspect that you are running images that do not contain your project files (this applies to the prod environment). Rebuilding the images should solve this problem.

Build new images for dev and prod environments (with explicitly disabling the build cache):

docker compose -f compose.yaml -f compose.override.yaml build --no-cache php
docker compose -f compose.yaml -f compose.prod.yaml build --no-cache php

Can you also clarify how exactly you tried to deploy the app in dev mode?

[upgrader-dev]

Thank you for your help @7-zete-7 .
I have tried many times rebuilding fresh images with --no-cache option without success.

I confirm that my server contains my project files as I can see them with visual studio code and a terminal running ssh.

I builded new images as you wrote above but when I deploy I get "container php is unhealthy".

To build the app in dev mode, I run

SERVER_NAME=your-domain-name.example.com \
APP_SECRET=ChangeMe \
CADDY_MERCURE_JWT_SECRET=ChangeThisMercureHubJWTSecretKey \
docker compose -f compose.yaml up -d --wait

My thoughts were : As the docker compose.yaml works on my local machine, there must be an issue with compose.prod.yaml

[7-zete-7]

Thanks for the info @upgrader-dev!

Did I understand correctly: you have the entire project (PHP, JS, etc. files) on the target server and on this target server you use the command ... docker compose -f compose.yaml -f compose.prod.yaml up ... to deploy the project?

[upgrader-dev]

Yes that’s right. 

[7-zete-7]

@upgrader-dev, this is a bit different from how Docker is usually used. The usual use case is to build a Docker image of a project and run it on a target server. There should be no project files on the target machine, they will already be included in the image.

More detailed information on how to do this can be found in the official Docker documentation (see https://docs.docker.com/get-started/workshop/).

One way to accomplish this:

1. Define the value of the environment variable IMAGES_PREFIX

   IMAGES_PREFIX=example.com/foo/bar- \
   docker compose ...

   or set the image tag of the image explicitly in the file compose.yaml

    services:
      php:
   -    image: ${IMAGES_PREFIX:-}app-php
   +    image: example.com/foo/bar-app-php

   These examples and below use the image tag example.com/foo/bar-app-php. This name needs to be changed and set according to the rules (see https://docs.docker.com/reference/cli/docker/image/tag/).

2. Build prod image locally

   docker compose -f compose.yaml -f compose.prod.yaml build --no-cache php

   See https://docs.docker.com/reference/cli/docker/compose/build/

3. Upload the built image to the image repository

   docker compose push php

   See https://docs.docker.com/reference/cli/docker/compose/push/

4. Get the necessary images on the target machine

   docker compose -f compose.yaml -f compose.prod.yaml pull

   See https://docs.docker.com/reference/cli/docker/compose/pull/

   On the target machine, it is enough to have only a few files from the entire project:

   • compose.yaml
   • compose.prod.yaml
   • .env

5. Run the project

   SERVER_NAME=my-project.example.com \
   APP_SECRET=!ChangeMe! \
   CADDY_MERCURE_JWT_SECRET=!ChangeThisMercureHubJWTSecretKey! \
   docker compose -f compose.yaml -f compose.prod.yaml up --wait --no-build

   See https://docs.docker.com/reference/cli/docker/compose/up/

---

If you need the project to work exactly the way you described (which I would not recommend doing for a number of reasons) — you need to add mounting of the project directory to the service container by adding the line to the compose.prod.yaml file:

 services:
   php:
     # ...
     volumes:
       # ...
+      - "./:/app"

Such mounting is usually used only during development. It is highly undesirable to deploy the project on the prod server in this way.

[upgrader-dev]

OK, I'll follow your directions and post results here, thank you.

[upgrader-dev]

So I followed your way of doing :

1. build images locally (and previously checked that they work locally)
2. push the images
3. pull images
4. docker compose...

and unfortunately I have the same results : the phpinfo displays instead of my home page...

I noticed a slight difference when running containers on the server or locally :

locally I have a container running a "mailer" image while I don't have it on production.

[7-zete-7]

Thanks for the reply, @upgrader-dev!

Can you try executing the following command on the target machine to make sure that the prod image is built correctly?
But replace example.com/foo/bar-app-php with your image.

docker container run --rm --entrypoint='' example.com/foo/bar-app-php ls -lh /app/ /app/src/ /app/vendor/

The command should return three non-empty lists.

Example of expected information

/app/:
total 1008K
-rw-r--r--  1 root root 3.9K Feb 20 13:32 .env
-rw-r--r--  1 root root    0 Feb 20 13:32 .env.dev
-rw-r--r--  1 root root 1.1K Feb 20 13:32 LICENSE
-rw-r--r--  1 root root 4.9K Feb 20 13:32 Makefile
drwxr-xr-x  2 root root 4.0K Feb 20 13:32 bin
-rw-r--r--  1 root root 7.2K Feb 20 13:32 composer.json
-rw-r--r--  1 root root 603K Feb 20 13:32 composer.lock
drwxr-xr-x  7 root root 4.0K Feb 20 13:32 config
drwxr-xr-x  2 root root 4.0K Feb 20 13:32 migrations
drwxr-xr-x  1 root root 4.0K Feb 20 13:35 public
<...>

/app/src/:
total 148K
drwxr-xr-x  4 root root 4.0K Feb 20 13:32 Api
drwxr-xr-x  2 root root 4.0K Feb 20 13:32 Command
drwxr-xr-x  6 root root 4.0K Feb 20 13:32 Controller
drwxr-xr-x  3 root root 4.0K Feb 20 13:32 DependencyInjection
drwxr-xr-x  5 root root 4.0K Feb 20 13:32 Entity
<...>

/app/vendor/:
total 172K
drwxr-xr-x 3 root root 4.0K Feb 20 13:35 api-platform
-rw-r--r-- 1 root root  771 Feb 20 13:35 autoload.php
-rw-r--r-- 1 root root  812 Feb 20 13:35 autoload_runtime.php
<...>

[upgrader-dev]

Here is the output of this command :
/app/:
total 8.0K
drwxr-xr-x 2 root root 4.0K Feb 19 11:45 public
drwxr-xr-x 2 root root 4.0K Mar 3 10:42 var
ls: cannot access '/app/src/': No such file or directory
ls: cannot access '/app/vendor/': No such file or directory

[7-zete-7]

Thanks for the quick response, @upgrader-dev!

It looks like your image is missing project files. Something probably went wrong during image build.

Can you run the image build command and show what build logs you receive?