You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Device and OS: Rockey9
App version: 0.49.0
Kubernetes distro being used: rke2 1.29
Other:
Steps to reproduce
Export Control Plane address, node port, and registry auth
Make sure git is not installed on machine
Run a zarf package mirror-resources
Expected result
I expected zarf to push the images and gitremotes however i got an error on git. Seems mirror-resources uses the host's git bin. This is different than when you use zarf package deploy which seems to use a packaged git library.
Actual Result
2025-02-24 16:47:05 INF pushing repository to server repo=https://repo1.dso.mil/big-bang/[email protected] server=
2025-02-24 16:47:07 ERR unable to push repo https://repo1.dso.mil/big-bang/[email protected] to the Git Server: All attempts fail:
#1: unable to fetch the git repo prior to push: exec: "git": executable file not found in $PATH
Visual Proof (screenshots, videos, text, etc)
Severity/Priority
Additional Context
Add any other context or screenshots about the technical debt here.
The text was updated successfully, but these errors were encountered:
To my knowledge - the use of the hosts git is only a fallback mechanism when the process cannot be supported by the go-git library.
Looking at your logs and the faq and example I believe the git url you are using should be supported by go-git - So there is definitely something to investigate further.
Environment
Device and OS: Rockey9
App version: 0.49.0
Kubernetes distro being used: rke2 1.29
Other:
Steps to reproduce
zarf package mirror-resources
Expected result
I expected zarf to push the images and gitremotes however i got an error on git. Seems mirror-resources uses the host's git bin. This is different than when you use
zarf package deploy
which seems to use a packaged git library.Actual Result
Visual Proof (screenshots, videos, text, etc)
Severity/Priority
Additional Context
Add any other context or screenshots about the technical debt here.
The text was updated successfully, but these errors were encountered: