Docker Cloud
JetBrains898a91e3-9a16-481a-b1a4-c959a7824350 · v—
Cloud Agent Plugin for Docker containers (build: 0d6c7029f4a30a1f642499cadaac2936748eb808, RELEASE).
Rating distribution
Reviews 8
Sorry, just saw you have a GitHub tracker, I'll post it there instead
Hi @reje - I have been using this with lots of success for quite a while, but yesterday I updated from 10.0.0.4 (I think) to 2017.2.2. Now, I get this error and I can't run my Docker builds any more: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'run.var.teamcity.cloud.docker.web.ContainerTestController#0': Failed to introspect bean class...
Hi swethapraj, This problem has probably no direct relation with the cloud plugin itself. All interactions with the Docker daemon are performed using the Docker REST API (it never tries to invoke the Docker binaries directly). You most likely have a build step that rely on the Docker client executable to be available to the agent, and this dependency is not met. Hope this helps.
hi reje, i was able to integrate docker cloud plugin on TC server. I'm getting below error where it is not able to recognize docker command. any bkm/thoughts? [19:18:07][Step 3/4] [19:18:07][Step 3/4] Directory of C:\ [19:18:07][Step 3/4] [19:18:07][Step 3/4] 11/29/2017 06:14 PM BuildAgent [19:18:07][Step 3/4] 11/22/2016 02:45 PM 1,894 License.txt [19:18:07][Step 3/4] 07/16/2016 05:18 AM ...
Hi swethapraj, you may encounter this error if you have a Docker cloud profile without any agent image defined (you need at least one). A validation handler should actually prevent to create/save such empty profile but right now it does not work as it should. This will be fixed in the release. Don't hesistate to use the github issue trackers to report new issues...
Hi Reje, We have evaluating the docker cloud plugin for TC 10.0.4. We are having below error. Any thoughts or BKM sharing on the issue? Is there any other config we need to refer to get things working? Failed to initialize cloud client 'VRDC'.Invalid thread pool size: 0 Hide stacktrace java.lang.IllegalArgumentException: Invalid thread pool size: 0 at...
When assigning an agent to an agent pool (in the "Pools" tab of the "Agents" menu) you have the choice to select an individual agent or a specific cloud image. It would also be possible to make this settings available directly from the cloud image settings page, but this feature is not planned yet. If something is not working as expected (or for any other question), I suggest opening an issue...
How to assign docker teamcity agent to particular pool instead of Default pool.
Similar in “Cloud”
Qoder CN (Formerly Lingma) - Alibaba Cloud AI Coding Assistant
tongyi-lingma
Kubernetes
JetBrains
Big Data Tools
JetBrains
Aspire
JetBrains
Remote File Systems
JetBrains
Azure Toolkit for Rider
JetBrains