argo-cd: Unable to create new app on localhost

Checklist:

  • I’ve searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
  • I’ve included steps to reproduce the bug.
  • I’ve pasted the output of argocd version.

Describe the bug

Unable to create application: application spec for guestbook is invalid: 
InvalidSpecError: repository not accessible: 
rpc error: code = Unknown desc = error testing repository connectivity: 
Get "https://github.com/argoproj/argocd-example-apps.git/info/refs?service=git-upload-pack": 
dial tcp: lookup github.com on 10.96.0.10:53: server misbehaving

To Reproduce Follow the steps available at argocd docs. https://argo-cd.readthedocs.io/en/stable/getting_started/

Expected behavior The application should be created.

Screenshots image

Version

Paste the output from `argocd version` here.
➜  ~ argocd version 
argocd: v2.2.5+8f981cc
  BuildDate: 2022-02-05T01:33:25Z
  GitCommit: 8f981ccfcf942a9eb00bc466649f8499ba0455f5
  GitTreeState: clean
  GoVersion: go1.16.11
  Compiler: gc
  Platform: linux/amd64

Logs

Paste any relevant application logs here.
➜  ~ kubectl port-forward --address 0.0.0.0 svc/argocd-server -n argocd 8080:443    
Forwarding from 0.0.0.0:8080 -> 8080
Handling connection for 8080
Handling connection for 8080
Handling connection for 8080
Handling connection for 8080
Handling connection for 8080
Handling connection for 8080
Handling connection for 8080
Handling connection for 8080
Handling connection for 8080
Handling connection for 8080
Handling connection for 8080
Handling connection for 8080
Handling connection for 8080
Handling connection for 8080
Handling connection for 8080
Handling connection for 8080
Handling connection for 8080
Handling connection for 8080
Handling connection for 8080
E0302 16:24:34.627761   89059 portforward.go:378] error copying from remote stream to local connection: readfrom tcp4 127.0.0.1:8080->127.0.0.1:42386: write tcp4 127.0.0.1:8080->127.0.0.1:42386: write: broken pipe
Handling connection for 8080
Handling connection for 8080
Handling connection for 8080
Handling connection for 8080
E0302 16:25:05.346601   89059 portforward.go:378] error copying from remote stream to local connection: readfrom tcp4 127.0.0.1:8080->127.0.0.1:42424: write tcp4 127.0.0.1:8080->127.0.0.1:42424: write: broken pipe
E0302 16:26:17.346894   89059 portforward.go:378] error copying from remote stream to local connection: readfrom tcp4 127.0.0.1:8080->127.0.0.1:42452: write tcp4 127.0.0.1:8080->127.0.0.1:42452: write: broken pipe
Handling connection for 8080
Handling connection for 8080
Handling connection for 8080
Handling connection for 8080
Handling connection for 8080
Handling connection for 8080
E0302 16:26:47.346909   89059 portforward.go:378] error copying from remote stream to local connection: readfrom tcp4 127.0.0.1:8080->127.0.0.1:42764: write tcp4 127.0.0.1:8080->127.0.0.1:42764: write: broken pipe
Handling connection for 8080
Handling connection for 8080
Handling connection for 8080
Handling connection for 8080
Handling connection for 8080
Handling connection for 8080
Handling connection for 8080
Handling connection for 8080
Handling connection for 8080
Handling connection for 8080
Handling connection for 8080
Handling connection for 8080
E0302 16:50:49.347484   89059 portforward.go:378] error copying from remote stream to local connection: readfrom tcp4 127.0.0.1:8080->127.0.0.1:54498: write tcp4 127.0.0.1:8080->127.0.0.1:54498: write: broken pipe
Handling connection for 8080
Handling connection for 8080
E0302 16:54:55.347098   89059 portforward.go:378] error copying from remote stream to local connection: readfrom tcp4 127.0.0.1:8080->127.0.0.1:54928: write tcp4 127.0.0.1:8080->127.0.0.1:54928: write: broken pipe
E0302 16:58:07.346812   89059 portforward.go:378] error copying from remote stream to local connection: readfrom tcp4 127.0.0.1:8080->127.0.0.1:54536: write tcp4 127.0.0.1:8080->127.0.0.1:54536: write: broken pipe



About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 15

Most upvoted comments

Fair. Those docs aren’t super clear to me, but I guess it’s sufficient. Thanks for investigating!

This time I choose VirtualBox as the VM-driver using minikube.

It worked fine with VirtualBox, I’m still troubleshooting with vm-driver=docker

minikube start --driver=virtualbox

Able to add App

image