Clone Git repo with submodules
We can successfully clone our Git repo (with both https and ssh), but as soon as it has submodules (from the same server), the cloning of the submodule fails with an authentication error. Same thing happens when using SSH keys. Cloning and deploying standalone Git repos without submodules works fine, and as far as I could see, if the submodule is a public repo (for instance on Github), it would clone as well.
Setup: Dokploy 0.10.10 on an Azure VM with Ubuntu 24.04; Git repos are on Azure DevOps.
8 Replies
To add to that: on local dev machines, and on our CI/CD build server, the clone and build process works. I assume that Git Credential Manager handles the authentication for the submodules on those machines.
you can see more details here
I think is the same as here
GitHub
Submodules cloning fails using GitHub provider · Issue #621 · Dokpl...
To Reproduce Create an application using a GitHub provider selecting a repository with a private submodule owned by the same GitHub account. Try to deploy the application. Cloning of the submodule ...
Not quite @Siumauricio - the repo I clone also fails to pull up the submodules from the same Git provider with the same credentials over HTTPS.
The main repo is a monorepo which has two submodules. One submodule is a public Github repo, that one works, the second submodule is a private Git repo from the same source/provider as the main repo. Both submodules have been initialized and linked into the main repo with HTTPS URLs.
Both main and public submodule clone fine when using either HTTPS or SSH, and the private submodule always fails.
The workaround for now is to build Docker images in Azure, their build agents pull all repos just fine, and push the images to a registry which notifies Dokploy. But this is not what I think is the most slim and easy structure for deploying and running 60+ microservices.
Are you using Github provider or Git?
Git provider - the private repos are on Azure DevOps. Only the public repo is on Github.
Ok, for the Git Provider are you using SSH?
or HTTP?
I tried both. SSH first, I added a key in dokploy and in the repo and used the Dokploy UI to clone. For HTTPS however, I had to use the repo URL and manually put user:password like https://user:[email protected]/...
After I read the bug on Github you mentioned above, I tried HTTPS, but it didn't work either.