getwud / wud

WUD (aka What's up Docker?) gets you notified when a new version of your Docker Container is available.
https://getwud.github.io/wud/
MIT License
1.26k stars 39 forks source link

Error when processing #470

Open chong206 opened 3 weeks ago

chong206 commented 3 weeks ago

report errors Redeploy, still reporting an error getwud/wud:latest 2024 — WUD (version latest)

Error when processing (Error: Client network socket disconnected before secure TLS connection was established Error when processing some containers (Cannot read properties of undefined (reading 'tag'))

截图_20241028190350

log WUD (2).txt WUD (3).txt

fmartinou commented 1 week ago

Weird.

Where are your images from? Docker Hub?

Do you have any networking stuff that could prevent wud from performing Https requests to public registries?

chong206 commented 1 day ago

@fmartinou Yes, it is. It's all pulled from Docker Hub. It still fails after the update, I'm connecting through a proxy. The network should be fine. Other containers also access through this proxy without any problems, access is fine. 01 02 03

WUD.txt

docker create \ --name WUD \ --privileged \ -v "/var/run/docker.sock:/var/run/docker.sock" \ -v "/volume1/docker/WUD/":/store \ -p 3000:3000 \ -e TZ="Asia/Shanghai" \ -e WUD_AUTH_BASIC_c_USER="" \ -e WUD_AUTH_BASIC_c_HASH="" \ -e WUD_TRIGGER_SMTP_QQ_HOST="" \ -e WUD_TRIGGER_SMTP_QQ_PORT="" \ -e WUD_TRIGGER_SMTP_QQ_USER="" \ -e WUD_TRIGGER_SMTP_QQ_PASS="" \ -e WUD_TRIGGER_SMTP_QQ_FROM="" \ -e WUD_TRIGGER_SMTP_QQ_TO="" \ -e WUD_TRIGGER_SMTP_QQ_ONCE="false" \ -e WUD_WATCHER_LOCAL_CRON="0 10 *" \ -e WUD_TRIGGER_SMTP_QQ_SIMPLETITLE="容器《\${name}》有新版本\${semver},请更新。" \ -e WUD_TRIGGER_SMTP_QQ_SIMPLEBODY="容器《\${name}》有新版本\${semver},请更新。可以从版本:\${local} 。更新到版本:\${remote}" \ -e WUD_REGISTRY_HUB_LOGIN="" \ -e WUD_REGISTRY_HUB_PASSWORD="" \ --restart unless-stopped \ -e HTTP_PROXY=http://...: \ -e HTTPS_PROXY=http://...: \ getwud/wud:latest

fmartinou commented 20 hours ago

I'm not sure that the http client configured to query the registry automatically handles the HTTP_PROXY HTTPS_PROXY env vars 🤔 ; I need to check.