Docker.hub is not accessible from Russia

Docker Hub
1

Why was this restriction introduced?

$ docker pull nginx
Using default tag: latest
Error response from daemon: pull access denied for nginx, repository does not exist or may require 'docker login': denied: <html><body><h1>403 Forbidden</h1>
Since Docker is a US company, we must comply with US export control regulations. In an effort to comply with these, we now block all IP addresses that are located in Cuba, Iran, North Korea, Republic of Crimea, Sudan, and Syria. If you are not in one of these cities, countries, or regions and are blocked, please reach out to https://hub.docker.com/support/contact/
9 Likes
2

Issuing same here. Khimki, Russia. Maybe something with providerā€™s IP?
Main issue here - not being able to contact [https://hub.docker.com/support/contact/ ]

2 Likes
3

Same story here. Barnaul, Russia and a Yandex cloud host.

sudo docker pull python ī‚² 1 āœ˜

Using default tag: latest
Error response from daemon: pull access denied for python, repository does not exist or may require ā€˜docker loginā€™: denied:

403 Forbidden


Since Docker is a US company, we must comply with US export control regulations. In an effort to comply with these, we now block all IP addresses that are located in Cuba, Iran, North Korea, Republic of Crimea, Sudan, and Syria. If you are not in one of these cities, countries, or regions and are blocked, please reach out to https://hub.docker.com/support/contact/

1 Like
4

Same here for St. Petersburg, Russia.

Please consider keeping dockerhub available for russians - theyā€™re oppressed by their own government they didnā€™t choose.

The regime will have access to any technology anyway, and have resources to keep their infrastructure running.

Itā€™s people of Russia who are suffering from US sanctions as theyā€™re currently implemented, not the elites who keep doing evil things.

4 Likes
5

Same for me, Russia, YandexCloud
While doing ā€˜docker loginā€™ got an error:
Error response from daemon: login attempt to https://registry-1.docker.io/v2/ failed with status: 403 Forbidden

12

It looks like this is due to a new law/sanction which is not decided by Docker Inc, so they have to follow it whether we agree with it or not. You are free to agree or disagree with it, but this is not a political forum so please, try not to share political opinions and definitely try not to insult anyone. I deleted some posts and rejected some of the posts that were blocked by the automatic spam filter, becuse these posts contained inappropriate language or insults or just replied to one of those so users would not understand what those replied to.

This is a community forum to support Docker users, but we canā€™t block anyone on the Docker Hub or anywhere else. If it is indeed due to a U.S. law, the Docker staff canā€™t help unfortunately. Please, continue civilized discussions avoiding political contents and insults.

If any of you think you were blocked by mistake and canā€™t access the contact form on Docker Hub either, you can try a VPN or open a ticket on GitHub

Thank you for your understanding.

1 Like
13

Is there an official confirmation that docker has stopped working in the Russian Federation?

14

This is the last I know about:

But it was about business, not accessing the services. I havenā€™t read any official announcement about the new rules yet, but I didnā€™t have time to search for it either.

1 Like
15

What law? Hub is just a file sharing in a nutshell. And Docker already donā€™t work in Russia. Iā€™m sure blocking IPs is a voluntary action of company.

1 Like
16

Even if it is, it is their right)

2 Likes