davidmine
commented
5 years ago I'm having similar problems with a windows agent. I'm running windows docker container within a Teamcity server deployed on Azure. The agent starts, but never registers any runners or parameters. I get this error 
, but I don't believe it. If the agent didn't have the server-url properly configured, how would the server know to display the agent? My best guess is that some other configuration setting is causing the launch to break and that's why the agent has no listed runners
I'm able to pull the docker image to my local machine, run the container, and have the agent successfully connect to the server deployed on Azure. I know that the docker image works without any modification.
My next thought was that the Teamcity server version was the problem. I was able to successfully update the "Deploy to Azure" server instance to 2019.2.1 (including a few VM reboots for good measure), but that didn't solve the problem either. At this point, my logs are pretty jumbled between all the stuff that I tried, but I would be happy to delete everything, start again with a specific test, and upload those logs.
Any update on this?
undimmable
Description
I try to use the teamcity windows agent docker images within azure. Unfortunately, that doesn't work as expected. As you can see in the agent log, some operations to generate the configuration file fails.
I guess that's because there is no storage account attached to the container. But the UI only let my attach a storage account on the linux image (which starts and connects fine).
If you need any more data, please let me know! Thank you very much for your help.
Environment
Diagnostic logs
agent-log.txt
