Run Azure Pipelines in Docker - Flexible Scalable CICD 

Yes, absolutely. You'd just have to install docker in it yourself

I will try my best.

Each job runs on a different agent (VM), and every time an agent is instantiated it’s “clean”. That is why the cache is not there. You could try using the cache task (I have a video about it) but I wouldn’t recommend using it for such a big “file” as a container image is…

Hi. That's a tricky question, because it depends on how big your machine is and what you have to do with the agents. :) In theory you should assign at least 1 core and 1 Gb of ram to each container. But then it may not be enough if you need to perform cpu and/or memory intensive task. Building a large solution with 1 core may take long time, and 1gb of Ram may not be enough and your agent may run out of memory. Ultimately, depends on what you have to do :)

Thanks for the compliments :) I;' not sure what you mean... If you used the install script, the pipeline service should start automatically every time the container starts

Hye. I'm not sure I understand the question. What is your use case, and what do you want to achieve? :)

@@CoderDave I did all the tutorial . But i have an error when i run the script start.ps1 after step 1 when it says is downloading the vsts agent at step 2 i got an error . Question is, if i download the vsts agent and install it manually will result in the same output as if my start.ps1 script will succefully run ?

and I should mention I do have a start.sh script in the same folder as my dockerfile

The EXEC command executes something inside the container. And that it expect that “something” to be already inside the container

@@CoderDave Thank you for the reply! Shouldnt start.sh be in the container from the copy ./start.sh . ?

If anyone else runs into this issue what fixed it for me was switching ./start.sh from CRLF to LF in notepad++

Oh wow, the “classic” Windows vs Linux line termination issue 😅