Portainer does not pull the entire git repo before computing the docker-compose.yml

[LeVraiRoiDHyrule]

Ask a Question!

Hi,
All my Portainer stacks are pulled from git repositories.
In my compose, I have the following:

configs:
  synapseconfig:
    file: synapseconfig.yaml

In the git repository, synapseconfig.yaml is at the right place, alongside docker-compose.yml

But when pulling, Portainer throws the following error:
Failed to deploy a stack: compose up operation failed: Error response from daemon: invalid mount config for type "bind": bind source path does not exist: /data/compose/119/config/synapseconfig.yaml

This file should exists as it is in the right place in the git repo. According to https://docs.portainer.io/user/docker/stacks/add#option-3-git-repository, Portainer should be pulling the entire repo to /data/compose/119/config/. But it does not. I noticed than when pulling, Portainer does the following:

1. Clear entire /data/compose/119/config/ directory
2. Try to compute only the docker-compose.yml (which fails as it has not pulled all other files)
3. Pull the entire git repo

At the end, synapseconfig.yaml is present in /data/compose/119/config/, but not when Portainer computes the docker-compose.yml.

Am I doing something wrong ?

Thanks in advance for any answer

[LeVraiRoiDHyrule]

Hi, would someone have an idea about this issue ?

I am on 2.27.3 LTS CE version, and I still have this issue.
Thanks in advance for any answer

[Nick-Portainer]

Hi @LeVraiRoiDHyrule Are you using relative pathing, it's a setting in the repository deployment screen that will download the entire repo before deploying.

[LeVraiRoiDHyrule]

Thanks a lot for your answer.

I can see that relative pathing is exclusive to the business edition. That is very inconvenient, is there a workaround with community edition ? Is there a way to reference another file as a config file, and have it parsed by compose so that the env variable placeholders in that config file are replaced ?

So far I only used configs top level element with inline content directly in the compose file. It works and env variable placeholders are replaced. But now I have much bigger config files that I want in another file, hence my current problem.

https://docs.portainer.io/user/docker/stacks/add#option-3-git-repository says the following : When a stack is deployed from Git, Portainer will clone the entire Git repository as part of the deployment process. Ensure you have enough free space to accommodate this. . Is it no longer the case ?

Thanks in advance for any answer.

[Entropy512]

If you're on CE, you need to use absolute paths:
Replace any occurrence of ./ in the docker-compose file with ${INSTALL_PATH:-.}
Check out the repo somewhere on the host
Set INSTALL_PATH in the stack's environment variables to the path to that repo
Ensure that any time you make changes to the git repo, you pull to the local install path