blocks|key|4374729|text|如果您使用的是Docker+Hub，您可以使用Webhook通知docker主机更新，并对此采取行动。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4374730|使用webhook将是一种“简单”的方法(我认为)，否则您将不得不在docker+pull中进行某种爬行，或者正如@alebianco所解释的那样，比较一些散列或构建/创建日期。|4374731|下面是关于它的文档：https://docs.docker.com/docker-hub/webhooks/|offset|length|4374732|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.docker.com/docker-hub/webhooks/^0|0|0|A|18|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@$F|S|G|T|1|U]]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

If you are using Docker Hub you could use a Webhook to notify the docker host about a update, and take action over that.

Using the webhook would be the "simple" way to do it (I think) otherwise you would have to do some kind of crawling in the docker pull or as explained by @alebianco comparing some hashs or build/creation dates.

Here is the docs about it: <a href="https://docs.docker.com/docker-hub/webhooks/" rel="nofollow noreferrer">https://docs.docker.com/docker-hub/webhooks/</a>

blocks|key|4375210|text|我用一个爬虫解决了这个问题，它可以直接检查Dockerfile，也可以检查from字符串。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4375211|我把所有的东西都备份到了一个可以在docker+hub中找到的docker镜像中。|4375212|我只需在我的gitlab+ci管道中运行该映像。如果基础图像已过时，则会打印所有较新的版本，以便您可以轻松地选择标签。|4375213|链接：https://hub.docker.com/r/olafnorge/docker-image-crawler/|4375214|entityMap|0|LINK|mutability|MUTABLE|url|https://hub.docker.com/r/olafnorge/docker-image-crawler/|1^0|11|4|0|H|A|0|0|0|3|1K|1|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@]|D|@$9|Y|A|Z|1|10]]|E|$]]|$1|H|3|I|5|6|7|11|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|12|8|@]|D|@$9|13|A|14|1|15]]|E|$]]|$1|L|3|-4|5|6|7|16|8|@]|D|@]|E|$]]]|M|$N|$5|O|P|Q|E|$R|S]]|T|$5|O|P|Q|E|$R|S]]]]

I solved this issue with a crawler that checks either the Dockerfile directly or a <code>from</code> string.

I backed everything into a docker image which could be found in the <a href="https://hub.docker.com/r/olafnorge/docker-image-crawler/" rel="nofollow noreferrer">docker hub</a>.

I simply run the image in my gitlab ci pipeline. If the base image is outdated is prints all newer versions so that you can easily pick the tag.

Link: <a href="https://hub.docker.com/r/olafnorge/docker-image-crawler/" rel="nofollow noreferrer">https://hub.docker.com/r/olafnorge/docker-image-crawler/</a>

blocks|key|4375270|text|您可以查询注册表API以获取图像摘要，并将其与您拉取的图像摘要进行比较。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4375271|$+cat+digest-v2.sh
#!/bin/sh

ref="${1:-library/ubuntu:latest}"
repo="${ref%25:*}"
tag="${ref##*:}"
acceptM="application/vnd.docker.distribution.manifest.v2%2Bjson"
acceptML="application/vnd.docker.distribution.manifest.list.v2%2Bjson"
token=$(curl+-s+"https://auth.docker.io/token?service=registry.docker.io&scope=repository:${repo}:pull"+\
++++++++%7C+jq+-r+'.token')
curl+-H+"Accept:+${acceptM}"+\
+++++-H+"Accept:+${acceptML}"+\
+++++-H+"Authorization:+Bearer+$token"+\
+++++-I+-s+"https://registry-1.docker.io/v2/${repo}/manifests/${tag}"

$+./digest-v2.sh+library/busybox:latest
HTTP/1.1+200+OK
Content-Length:+2080
Content-Type:+application/vnd.docker.distribution.manifest.list.v2%2Bjson
Docker-Content-Digest:+sha256:d366a4665ab44f0648d7a00ae3fae139d55e32f9712c67accd604bb55df9d05a
Docker-Distribution-Api-Version:+registry/2.0
Etag:+"sha256:d366a4665ab44f0648d7a00ae3fae139d55e32f9712c67accd604bb55df9d05a"
Date:+Sun,+11+Oct+2020+21:04:59+GMT
Strict-Transport-Security:+max-age=31536000|code-block|syntax|javascript|4375272|您可以将该ETag或Docker-Content-Digest标头与之前拉取的图像上的注册表引用进行比较：|4375273|$+docker+image+inspect+busybox:latest+--format+'{{json+.RepoDigests}}'+%7C+jq+.
[
++"busybox@sha256:d366a4665ab44f0648d7a00ae3fae139d55e32f9712c67accd604bb55df9d05a"
]

$+docker+image+pull+busybox:latest
latest:+Pulling+from+library/busybox
Digest:+sha256:d366a4665ab44f0648d7a00ae3fae139d55e32f9712c67accd604bb55df9d05a
Status:+Image+is+up+to+date+for+busybox:latest
docker.io/library/busybox:latest|4375274|我还一直在开发一些Go+API和CLI，以便在您可能需要传递不同类型授权的更多注册表中工作。该项目位于regclient/regclient，其中包含一个regctl命令。|offset|length|style|CODE|4375275|$+regctl+image+digest+--list+busybox:latest
sha256:d366a4665ab44f0648d7a00ae3fae139d55e32f9712c67accd604bb55df9d05a|4375276|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/regclient/regclient^0|0|0|0|0|25|6|1F|J|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|12|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|13|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|14|8|@$M|15|N|16|O|P]]|9|@$M|17|N|18|1|19]]|A|$]]|$1|Q|3|R|5|D|7|1A|8|@]|9|@]|A|$E|F]]|$1|S|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z]]]]

You can query the registry API for the image digest and compare it to that of what you've pulled.
<pre><code>$ cat digest-v2.sh
#!/bin/sh

ref=&quot;${1:-library/ubuntu:latest}&quot;
repo=&quot;${ref%:*}&quot;
tag=&quot;${ref##*:}&quot;
acceptM=&quot;application/vnd.docker.distribution.manifest.v2+json&quot;
acceptML=&quot;application/vnd.docker.distribution.manifest.list.v2+json&quot;
token=$(curl -s &quot;https://auth.docker.io/token?service=registry.docker.io&amp;scope=repository:${repo}:pull&quot; \
 | jq -r '.token')
curl -H &quot;Accept: ${acceptM}&quot; \
 -H &quot;Accept: ${acceptML}&quot; \
 -H &quot;Authorization: Bearer $token&quot; \
 -I -s &quot;https://registry-1.docker.io/v2/${repo}/manifests/${tag}&quot;

$ ./digest-v2.sh library/busybox:latest
HTTP/1.1 200 OK
Content-Length: 2080
Content-Type: application/vnd.docker.distribution.manifest.list.v2+json
Docker-Content-Digest: sha256:d366a4665ab44f0648d7a00ae3fae139d55e32f9712c67accd604bb55df9d05a
Docker-Distribution-Api-Version: registry/2.0
Etag: &quot;sha256:d366a4665ab44f0648d7a00ae3fae139d55e32f9712c67accd604bb55df9d05a&quot;
Date: Sun, 11 Oct 2020 21:04:59 GMT
Strict-Transport-Security: max-age=31536000
</code></pre>
You can compare that ETag or Docker-Content-Digest header to the registry reference on the image you've previously pulled:
<pre><code>$ docker image inspect busybox:latest --format '{{json .RepoDigests}}' | jq .
[
 &quot;busybox@sha256:d366a4665ab44f0648d7a00ae3fae139d55e32f9712c67accd604bb55df9d05a&quot;
]

$ docker image pull busybox:latest
latest: Pulling from library/busybox
Digest: sha256:d366a4665ab44f0648d7a00ae3fae139d55e32f9712c67accd604bb55df9d05a
Status: Image is up to date for busybox:latest
docker.io/library/busybox:latest
</code></pre>
I've also been working on some Go APIs and CLI to work with more registries where you may need to pass different types of authorization. That project is at <a href="https://github.com/regclient/regclient" rel="noreferrer">regclient/regclient</a> and includes a <code>regctl</code> command.
<pre><code>$ regctl image digest --list busybox:latest
sha256:d366a4665ab44f0648d7a00ae3fae139d55e32f9712c67accd604bb55df9d05a
</code></pre>

I'm running a react app in a docker container, on a Coreos server. Let's say it's been pulled from dockerhub from <code>https://hub.docker.com/r/myimages/myapp</code>.

Now I want to check periodically if the dockerhub image for the app container has been updated, to see if the image I'm running locally is behind.

What would be the most efficient way to check if a local docker image is outdated compared to the remote image? All solutions I've found so far are bash scripts or external services that push on an update. I'd like to find a solution that is as native to docker as possible, and would like to refrain from pushing a notification from somewhere else (to alert the server of an updated image).

How do I check if my local docker image is outdated, without pushing from somewhere else?

服务器

容器

Docker

我正在Coreos服务器上的docker容器中运行react应用程序。假设它是从https://hub.docker.com/r/myimages/myapp的dockerhub中提取出来的。现在，我想定期检查应用程序容器的dockerhub镜像是否已更新，以查看我在本地运行的镜像是否落后。与远程映像相比，检查本地do...

问如何在不从其他地方推送的情况下检查本地docker镜像是否过时？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在不从其他地方推送的情况下检查本地docker镜像是否过时？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在不从其他地方推送的情况下检查本地docker镜像是否过时？
EN