Right now these instructions are "paste these files onto your computer and build it yourself". MS has a public Dockerhub account https://hub.docker.com/u/microsoft/ where officially-built images can be hosted and distributed. Just a good-practice suggestion
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
Strange thing is there's this: https://hub.docker.com/_/microsoft-azure-pipelines-vsts-agent?tab=description
This seems to be deprecated, according to its docs. Why? Also those images are pretty old (22-1-2019).
This has recent releases posted in GitHub, but unfortunately does not seem to be for docker: https://github.com/Microsoft/azure-pipelines-image-generation
@kwaazaar yes I can't figure out why they would deprecate those images, makes no sens to me.
Copy and pasting scripts is error prone, inheriting from an image is not.
Hi everybody, I created a Docker image on the hub which contains .NET Core 3 SDK, Docker within Docker, SQL Server commands clients and more --> wizzapi/azpdockeragent
It's a fork of microsoft-azure-pipelines-vsts-agent:ubuntu-16.04-docker-18.06.1-ce-standard
Microsoft are incredibly confused about their build agent strategy. Deprecating the Docker agents in favour of Packer was a terrible idea considering how much more effort Packer builds in comparison.
The Dockerhub images and the Helm chart were perfect, easily integrated into things like Kubernetes or ACI. Literally took 5 minutes effort to deploy build agents across our clusters.
Now we have to deal with this rubbish.
This issue hasn't been updated in more than 180 days, so we've closed it. If you feel the issue is still relevant and needs fixed, please reopen it and we'll take another look. We appreciate your feedback and apologize for any inconvenience.
Most helpful comment
Microsoft are incredibly confused about their build agent strategy. Deprecating the Docker agents in favour of Packer was a terrible idea considering how much more effort Packer builds in comparison.
The Dockerhub images and the Helm chart were perfect, easily integrated into things like Kubernetes or ACI. Literally took 5 minutes effort to deploy build agents across our clusters.
Now we have to deal with this rubbish.