Artifactory domains to allow when running self-hosted runners under a firewall.
Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.
Summary
When running Bitbucket pipeline builds with a self-hosted runner under a firewall you will have to ensure to allow traffic for all Atlassian artifactories. Otherwise, users may experience failures like this:
1
Unable to pull image: Head \"https://k8s-docker.packages.atlassian.com/v2/pause/manifests/3.8\": Get \"https://k8s-docker.packages.atlassian.com/api/docker/k8s-docker/v2/token?scope=repository%3Apause%3Apull&service=k8s-docker.packages.atlassian.com\": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)Solution
Here is the list of domains to allow:
1
2
3
4
5
docker-public.packages.atlassian.com
public.ecr.aws
docker-hub.packages.atlassian.com
k8s-docker.packages.atlassian.com
public.ecr.awsUpdated on April 24, 2025
Was this helpful?
Still need help?
The Atlassian Community is here for you.