Set Network For compose-unpacker

[CallMeJuf]

Ask a Question!

Hi, I was wondering if there was an option to set the network that portainer/compose-unpacker runs under.

For context I am trying to add a stack from a git repository that exists in a docker network.

Portainer can see the repository as I can add Portainer to that network. The Docker host also can see that repository via a reverse proxy or port mapping and hosts. In this scenario it all works as expected using the hostname of the container.

However when I Enable relative path volumes Portainer spawns compose-unpacker to clone the repo and it exists (I assume) in the default docker0 network. Because of this it cannot access my git repository.

[CodeMichael]

I have a similar situation, git is hosted on a tailscale tailnet and the requires the proper network figuration for access. Need to be able to specify the network configuration for compose-unpacker or I won't be able to checkout.

[31KM]

+1, I spent a whole day figuring this out.

I have an apps network that all my services are connected to. One of the services is Gitea. It hosts my docker stack YMLs.

Gitea IP: 10.168.10.3, so I used http://10.168.10.3:3000/MyUser/docker-stacks.git as repo URL while creating the stack. The immediate check done there gave a "context deadline exceeded" message and nothing was logged in portainer. While testing I let the portainer main container instance and the portainer agent container join the apps network which made this error go away. However, when clicking "deploy" it failed with an "I/O timeout". I looked at the unpacker logs which did not help. By coincidence I saw that the unpacker container instance only joined the default bridge network (172.17.0.0). When I made Gitea, portainer main and the portainer agent join the default bridge network it worked.
That also changes the repo URL used for the stack to http://172.17.0.2:3000/MyUser/docker-stacks.git (make sure to use IP assigned to your git hosting container)

This is unfortunate because AFAIK you cannot make a container created via docker compose stack automatically join the default bridge network and a user network. See for example the following issues in compose:

• Allow mixing of the default bridge with other networks docker/compose#3476
• Composefile v2 & default bridge network ERROR: b'Network-scoped alias is supported only for containers in user defined networks' docker/compose#3012

This means that I have to remember to manually make the Gitea container join the default bridge network or it won't work. Having the option to let the unpacker join the apps network that would be a whole lot easier.

Maybe I will raise this as an issue as well.

Some error messages that may people help find this:
In the portainer log withDEBUG enabled:
DBG github.com/portainer/portainer-ee/api/http/security/bouncer.go:423 > HTTP error | error="Get \"http://10.168.10.3:3000/MK13/docker-stacks.git/info/refs?service=git-upload-pack\": context deadline exceeded" msg="Git returned an error for listing refs" status_code=500

In the UI when under the repo URL input field:
Get "http://10.168.10.3:3000/MK13/docker-stacks.git/info/refs?service=git-upload-pack": context deadline exceeded

Also, keep in mind that the local filesystem path needs to be bind mounted in the agent container compose like

   volumes:
      - /opt/local_git_docker:/opt/local_git_docker

It has to be the exact same as given in the UI.

[31KM]

Features can only be requested via discussion so I created a new one here https://github.com/orgs/portainer/discussions/13028 as this one is a question.