You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Brand new to Windows runners, thanks for reading.
- step: &winrun
- cd src
- docker build -t example .
error during connect: Post "http://localhost:2375/v1.24/build?buildargs=%7B%7D&cachefrom=%5B%5D&cgroupparent=&cpuperiod=0&cpuquota=0&cpusetcpus=&cpusetmems=&cpushares=0&dockerfile=Dockerfile&labels=%7B%7D&memory=0&memswap=0&networkmode=default&rm=1&shmsize=0&target=&ulimits=null&version=1": dial tcp [::1]:2375: connectex: No connection could be made because the target machine actively refused it.
Hi @Casey Wise,
Thank you for reaching out to the community.
I checked this internally with our Pipelines team and this appears to be an issue where Pipelines is automatically setting DOCKER_HOST with the default host.
For that, would it be possible for you to empty it and try to run Docker commands again?
To empty the variable on Windows PowerShell, you can use the command below.
script: - $Env:DOCKER_HOST = "" - cd src - docker build -t example .
Hope it helps and do let me know how it goes.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.