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
A straightforward pipeline auths GCP and then lists out the buckets using a service account
403 - We're sorry, but this service is not available in your location
I can run the pipeline manually on the hetzner vps and it works fine, it's only when those commands are run in the runner does it fail. What could be different about running in the runner vs directly on the machine as far as ip/dns location?
Hi @Ryan Detzel,
I believe that the runner will use the public IP address of the host machine.
Could you please share the following details:
1) What type of runner are you using? Is it a Linux Docker, Linux Shell, MacOS, or a Windows runner?
2) What is the version of the runner?
3) What is the operating system (+ its version) of the hetzner vps?
4) If you execute the following commands prior to running the gcp commands a) on a terminal on the hetzner vps and b) during a runner build, by adding them in your bitbucket-pipelines.yml: is the output the same in both cases a) and b) ? Or do you see different IPs in the output?
curl -4 ifconfig.co/
curl -6 ifconfig.co/