Portainer从Git仓库部署Stack时容器构建失败求助

Let’s break down why your local docker-compose works but Portainer throws the Dockerfile not found error, and fix it step by step:

1. Check Portainer’s Git Context & Dockerfile Pathing #

Unlike local docker-compose, Portainer might not automatically detect the Dockerfile location if it’s not in the root of the Git repo or if you’re referencing a submodule/repo without explicit context.

• If your CatalogFrontEnd.git repo has the Dockerfile in a subdirectory (not the root), explicitly define both the context and Dockerfile path in your compose file:

  build:
    context: http://someaddres/CatalogFrontEnd.git
    dockerfile: ./src/Dockerfile  # Replace with your actual relative path
  

• If you originally used Git submodules: Portainer doesn’t pull submodules by default. When setting up the Git repo in Portainer, look for an option like "Recursive clone" or "Pull submodules" and enable it. This ensures all submodule content (including your Dockerfile) is fetched during deployment.

2. Verify Git Server Access & Authentication #

Your local machine can reach the Git server, but Portainer’s host might have network restrictions or missing credentials:

• Network access: Ensure the server running Portainer can ping/access http://someaddres (check firewalls, proxy settings, or internal network rules).
• Repo authentication: If your Git server requires login, make sure you’ve added the correct credentials (username/password or SSH key) when configuring the Git repo in Portainer. Without this, Portainer might only clone a partial or empty repo, leading to missing Dockerfiles.

3. Check Dockerfile Case Sensitivity #

Local systems (especially Windows) are case-insensitive, but Portainer typically runs on Linux where filenames are case-sensitive. Double-check that your file is named exactly Dockerfile (not dockerfile, DockerFile, or any variation).

4. Test with a Local Context (Debugging Step) #

To rule out Git-related issues, try cloning the CatalogFrontEnd.git repo directly onto the Portainer host server (e.g., into /opt/catalog-frontend), then update your compose file to use the local path:

build: /opt/catalog-frontend

If this works, the problem is definitely with how Portainer interacts with your Git server—go back to steps 1 and 2 to fix that.

5. Check Portainer’s Build Logs for Clues #

Don’t just rely on the generic "can’t locate Dockerfile" error. In Portainer, go to the failed stack’s logs (under Stacks > [Your Stack] > Logs) to see the full output. You might find clues like:

• "Failed to clone repo" (authentication/network issue)
• "No such file or directory" (wrong Dockerfile path)
• "Submodule not found" (missing recursive clone)

内容的提问来源于stack exchange，提问作者Harald