We use Octopus to deploy our vsts-agent(s) to our Kubernetes cluster to be used by our on-prem TFS. We had successfully deployed the image
microsoft/vsts-agent:ubuntu-16.04-tfs-2018-u2-docker-17.12.0-ce-standard out to our k8s cluster in September of 2018. We have an update we need to push out to our variables, and Octopus isn’t allowing us to use the
microsoft/vsts-agent repository. Octopus doesn’t seem to be able to retrieve or validate the versions/tags in the
We have the specific tag as part of the deployment step so it doesn’t accidentally target the wrong TFS version. When trying create a new release,
/tags is appended to the end of the entire URL it is searching for: which results in the following error “Request to `https://index.docker.io/v1/repositories/microsoft/vsts-agent:ubuntu-16.04-tfs-2018-u2-docker-17.12.0-ce-standard/tags` failed with NotFound:NOT FOUND.”.
We removed the specific tag from the step to see if we could select the version. The error generated by the addition of
/tags no longer happens, but Octopus still can’t search versions in the
microsoft/vsts-agent repository. When specifying the specific version (without selecting it) Octopus says
ubuntu-16.04-tfs-2018-u2-docker-17.12.0-ce-standard is not a valid version.
On-prem, we are using v2018.9.16, but I also tested this on our Octopus cloud account (v2018.11.1).
My question is, how can I deploy an update using the