Error when creating stack from Git source

[Copystrike]

Ask a Question!

Problem:

Every time I attempt to create a stack from a Git source in Portainer, I encounter the following error:

failed to deploy a stack: listing workers for Build: failed to list workers: Unavailable: connection error: desc = "error reading server preface: http2: frame too large"

Information:

• Portainer is distributed across two separate machines: one for the Portainer server and another for the agent.
• I access the Portainer website directly using the following IP address: https://192.168.3.206:9443/.
• It's worth noting that both the local machine and the agent are successfully connected.

Steps to Reproduce:

1. Log in to Portainer.
2. Navigate to the Stacks section.
3. Click on "Add Stack."
4. Select the option to create a stack from a Git source.
5. Enter the Git repository URL and other necessary information.
6. Attempt to create the stack.

Expected Behavior:

I expect the stack to be created successfully without encountering any errors.

Actual Behavior:

I receive the error message mentioned above when attempting to create the stack from a Git source.

Additional Information:

• Portainer version: Business Edition v2.19.0
• Host: Oracle Cloud Infrastructure

Screenshots:

(Example repo I found online)

Thanks for any possible help, if more information is required I'll try my best to provide so.

[Copystrike]

Turned this discussion into a issue since it seems to be a bug, #10301

[samdulam]

Does your compose have build function? Can you share it?
Are you using relative paths feature along with Git Stack, if not can you try using that.

[Copystrike]

Hey Samdulam,

Let me provide you with the requested information, the machine that I have:

Does your compose have build function? Can you share it?

Machine that only has the Portainer UI hosted (Will never have anything else):

Machine that has Portainer Agent installed (The machine that I am connected with to do a git build):

Are you using relative paths feature along with Git Stack, if not can you try using that.

Yes I am using relative paths in the docker-compose.yml

---

Also just want to tell you that my target machine (The Agent) never even get the chance to build anything. That is atleast everything I can assume from the logs.

Logs

Logs from machine with Portainer UI

Logs from machine with Portainer Agent

I assume the issue has something todo with the machine that host the Portainer UI, obviously this is an assumption

[Copystrike]

Hey,

I mistakenly, got relative paths confused with that from docker, turns out there is a setting in portainer you need to configure.
For anyone else having this issue issue message out: #10301 (comment)