TeamCity agent docker access denied creating buildAgent.properties
Answered
Hi,
I'm looking at migrating my VM agents to containers and currently use Windows agents. When I set up the container instances (I'm aware it's in preview, so might be buggy), everything ends up running ok, though the buildAgent.properties is never created, and the agent fails to start because of that. Here's a screenshot of the log output of the container
I was wondering if anyone else had this issue or could point me in the right direction
Please sign in to leave a comment.
Hi Daniel,
Please check the related comment in the YouTrack. Could you please try the provided solution and tell us if it'll help?
Hi Nadia,
Thank you for your reply. This is within Azure Container Instances, sorry for not clarifying earlier. Basically, I set up the cloud image inside TeamCity and it handles the Azure side on it's own, it doesn't look like I have any control over any 'docker run' or anything unfortunately
Hi Daniel,
As a workaround, you can try to use our '*-windowsservercore-*' agent images (the problem with process isolation doesn't exist in it). It's bigger, but at least, you can run an agent.
We'll try to investigate how permissions can be customized in Azure, and I'll get back if we find another solution. Sorry for the inconvenience.
Hi Nadia,
Thanks again for the quick reply :) I was trying those yesterday and it was working well. Unfortunately, windows containers don't have persistent storage like the linux ones do, and we need the windows ones (still investigating this) due to legacy dependencies and frameworks. This is a nice workaround, though downloading the image each time instead of caching it means it takes 10-15 minutes to run the container, even if it's in an Azure repository on the same subscription. For now, it's quicker to use the regular setup for our agents (image of a hard drive, spin up new vm). I'll wait until this is out of preview stage and revisit it then :)