🔧 Troubleshooting GitRunner Setup

During gitrunner setup using MobaXterm terminal, we encountered a few issues which we resolved through careful debugging and adjustments:

• Missing entrypoint.sh Error

  When we first attempted to run the container, we received an error stating: entrypoint.sh: No such file or directory. We confirmed the file existed in the correct path, but the issue persisted. Upon inspection, we realized the problem was due to Windows-style line endings (\\r\\n) introduced when the file was edited on a Windows system. To resolve this:

  • We ran sed -i 's/\\r$//' entrypoint.sh to convert the file to Unix line endings.
  • We also ensured the file was executable by running chmod +x entrypoint.sh.

• Container Failed with “Must not run with sudo”

  Another error occurred indicating the GitHub Actions runner must not run as the root user. This was due to the user: root line present in the docker-compose.yaml file. To fix this:

  • We commented out the user: root line in the docker-compose.yaml.
  • After saving the change, we rebuilt and restarted the container using docker-compose up -d --build.

🔧 Troubleshooting ArgoCD+ Repository Connection

<aside> 🏹

We had many failed attempts before we succesfully connected our Kubernetes repo to ArgoCD

</aside>

🔁 Attempt 1: Connect GitHub Repo via HTTPS

In Argo CD dashboard:

• Go to Settings → Repositories
• Click Connect Repository
• Method: HTTPS
  • Project: default
  • Repo URL: paste GitHub repo HTTPS link
  • Username: GitHub username (The_Cloud_Squad)
  • Password: GitHub PAT

❌ Connection FAILED

⚠️ Troubleshooting Attempt 1

• Verified steps
• Disconnected the failed connection via 3-dot menu
• Retried using all-lowercase credentials
• ❌ Still FAILED

🔁 Attempt 2: Switch to SSH Authentication

🔐 Generate SSH Key Pair

Open terminal (Git Bash or VS Code):

mkdir ~/.ssh/argocd-keys
cd ~/.ssh/argocd-keys
ssh-keygen -t ed25519 -C "[email protected]"

• Save without passphrase
  • Note the path to the keys