china ,docker，pull failed，help

[Dalishimin]

now 1.28.5 ，want to 1.29.1

nas has gone through the proxy and avoided blocking, but the problem still exists.

docker-compose --version

Docker Compose version v2.9.0-6413-g38f6acd

In the past, after entering such a command, the upgrade process was automatically completed.
docker-compose pull

but，now，i try many times，show：

if i retry，it show：

[+] Running 0/4
⠿ teslamate Error 7.0s
⠿ database Error 7.0s
⠿ grafana Error 7.0s
⠿ mosquitto Error 7.0s
Error response from daemon: Get "https://registry-1.docker.io/v2/": EOF

tks

[Dalishimin]

i retry

[Dalishimin]

compose file

i am sorry ,i don't know which file do u want.

[Dalishimin]

Can I get a preview of your compose file? It looks like something went wrong with your configuration.

always,the compose file's name like?
i am not a tech,3 years it works fine,pull ok
but from last month pull failed
now the imagine in aliyun
before I don't know how compose file work😓

[ShiriNmi1520]

If you have one, the filename should be docker-compose with the yml or yaml extension.
By the way, I saw your docker pull command; it looks like your aliyun registry can't find the teslamate image with the latest tag; can you confirm this on the aliyun site as well?

[Dalishimin]

get，tks
the compose file

and ,the teslamate image in aliyun

[Dalishimin]

get，tks the compose file

and ,the teslamate image in aliyun

@ShiriNmi1520 can u help me if the compose or the aliyun pull some wrong ,tks

[JakobLichterfeld]

You are using docker-compose which is deprecated and not supported. See hint https://docs.teslamate.org/docs/maintenance/backup_restore

If you are using docker-compose, you are using Docker Compose v1, which has been deprecated. Docker Compose commands refer to Docker Compose v2. Consider upgrading your docker setup, see Migrate to Compose V2

[JakobLichterfeld]

no, docker-compose != docker compose

[Dalishimin]

Now, it should be the v2 version. I tested 3 commands.
However, when pulling, the same error is still prompted:
Error response from daemon: Get "https://registry-1.docker.io/v2/": EOF

Another question is: I am using docker on Synology nas. After upgrading to v2, why do I keep getting the message:
WARN[0000] /volume1/docker/docker-compose.yml: the attributeversion is obsolete, it will be ignored, please remove it to avoid potential confusion

[JakobLichterfeld]

Error response from daemon: Get "https://registry-1.docker.io/v2/": EOF

docker.io indicates the Linux packages, not the docker container registry, therefore not a TeslaMate issue. Check your DNS, proxy, firewall, and region specific restriction.

Another question is: I am using docker on Synology nas. After upgrading to v2, why do I keep getting the message:
WARN[0000] /volume1/docker/docker-compose.yml: the attributeversion is obsolete, it will be ignored, please remove it to avoid potential confusion

You use in your docker-compose.yml the version tag at the beginning (for example version: 3), which is obsolete and can safely be deleted. See example docker-compose.yml here https://docs.teslamate.org/docs/installation/docker/

[Dalishimin]

maybe like @ShiriNmi1520 say:

Maybe it's because the government demands that Docker registry access be shut down. It looks like it's even affecting proxy servers.
For your reference, here's the post from JueJin to help you migrate the registry image to Aliyun

i tried ,but failed

[Dalishimin]

now ,other way,the last step ,trouble me,failed like this: