Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot start container #943

Closed
nixMark opened this issue Apr 30, 2017 · 4 comments
Closed

Cannot start container #943

nixMark opened this issue Apr 30, 2017 · 4 comments

Comments

@nixMark
Copy link

nixMark commented Apr 30, 2017

I have a docker cluster behind a VPN. And also I have a TFS on visualstudio.com, I have downloaded TFS agent container, and want to connect to our TFS but it cannot connect with an alarm of:

Determining matching VSTS agent...
Downloading and installing VSTS agent...
curl: (35) gnutls_handshake() failed: Error in the pull function.

gzip: stdin: unexpected end of file
tar: Child returned status 1
tar: Error is not recoverable: exiting now

It can ping google.But cannot ping public TFS. I would consider this as a network issue but nginx container was pulled and started with success.

  docker run \
  -e VSTS_ACCOUNT= xxx \
  -e TFS_HOST= yyy \
  -e VSTS_TOKEN= zzz \
  -it microsoft/vsts-agent

also tried this:

docker run \
  -e VSTS_ACCOUNT= xxx \
  -e VSTS_AGENT='$(hostname)-agent'\
  -e VSTS_TOKEN= yyy \
  -e TFS_URL= zzz \
  -e VSTS_POOL= eee \
  -e VSTS_WORK='/var/vsts/$VSTS_AGENT' \
  -v /var/vsts:/var/vsts \
  -it microsoft/vsts-agent:ubuntu-14.04

Although it is behind VPN, I can access the repo from browser btw.

@TingluoHuang
Copy link
Contributor

@HiraYuki base on the error, it doesn't looks like an agent issue, it's more like an image issue.

@nixMark
Copy link
Author

nixMark commented May 1, 2017

@TingluoHuang what exactly you would advise ? Image is not changed by me, it is default image from docker hub, which works on my local, but does not work on remote

@TingluoHuang
Copy link
Contributor

@HiraYuki i mean share your network config with the image owner, which is (Microsoft/vsts-agent-docker).
let them figure our how to make the image works on your environment.
I will cloes the issue for now, since the error looks like to be fail to download the agent package.

@alirezanet
Copy link

i have same problem ... did you fix that? @HiraYuki

prebansa pushed a commit to prebansa/azure-pipelines-agent that referenced this issue Aug 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants