Where are the stack deployment logs

[RampantDespair]

Ask a Question!

I'm currently trying to deploy a stack on Portainer, however it fails by stating that one of the containers is unhealthy.
Is it possible for me to access the extend logs for the deployment, so I can see the reason why said container is unhealthy?

Because when I deploy the stack using docker compose up everything works fine, but when I use Portainer, it doesn't.
So I am really curious about why that is.

Any help is appreciated.

[Nick-Portainer]

Do you get any information from the unhealthy container? Check under Stacks, click the stack in question and click the logs under quick actions for that container

[RampantDespair]

@Nick-Portainer
Even manually copy-pasting the docker-compose.yml into the web editor and uploading the .env file results in the same error.
Whereas with docker compose:

Any ideas about what the problem is?

[Nick-Portainer]

Hi @RampantDespair There's a few things here that I have noticed. One, you need to download the .env file and upload it into Portainer so it's aware of the environment varibles and can supply the values. The compose also uses relative paths so you need to make sure you have this enabled in your stack when deploying in Portainer.

Can you confirm you have done this? Otherwise Portainer is just grabbing that compose file and it won't be using the .env file by default.

[RampantDespair]

@Nick-Portainer
I'm currently trying to figure out a way to move these static volumes with relative paths automatically to a named volume so that there isn't any reliance on local volumes, as this is quite the annoyance.
I'll keep you posted, but I think you caught it; it has to be the paths

[RampantDespair]

Just to confirm when you said you need to upload the .env file to portainer for it to honor the values;
On the add stack page it says:

I have another stack running with the .env file directly inside the repository and didn't upload anything to portainer.
Portainer pulled it's environment variables directly from the repository and everything works as expected.

The compose also uses relative paths so you need to make sure you have this enabled in your stack when deploying in Portainer.

Enabled in what sense?

[Nick-Portainer]

Hi @RampantDespair,

I’ve done some testing with this repo, and it’s handling quite a lot. You’ll need to ensure you’re using relative paths, as that’s what this Compose file relies on. Additionally, make sure this setting is enabled in Portainer.

When using the CLI, it works because the pathing is handled automatically. However, in Portainer, you must explicitly define these paths, ensure they exist on your host, and verify that Portainer has access to them.

Enabled in what sense?

You will need to toggle the relative path in the Portainer UI, and make sure all the paths in this compose match where you are defining it in Portainer.