SUSE / Portus

Authorization service and frontend for Docker registry (v2)
http://port.us.org/
Apache License 2.0
3k stars 471 forks source link

Error writing events with webhook (Client.Timeout) and WebUI not updating. #2316

Open RyanLiu6 opened 4 years ago

RyanLiu6 commented 4 years ago

Description

I'm seeing this error all over the logs for the registry container. My configuration is shown below.

time="2020-07-21T07:17:58.750029836Z" level=error msg="retryingsink: error writing events: httpSink{https://some.server.com:12443/v2/webhooks/events}: error posting: Post https://some.server.com:12443/v2/webhooks/events: net/http: request canceled (Client.Timeout exceeded while awaiting headers), retrying" 
time="2020-07-21T07:17:58.750065575Z" level=warning msg="httpSink{https://some.server.com:12443/v2/webhooks/events} encountered too many errors, backing off" 

Steps to reproduce

  1. Run docker-compose up -d
  2. Push some images
  3. View the logs

Deployment information

Deployment method: I'm following the sample compose file configuration, with some modifications, which you can see below.

Configuration: Portus version: 2.5.0-dev@a1b9f2ebfeb84680a9dcd5629195e4c52815735c

Rake information for both portus and background containers can be found here Compose files and other configuration can be found here.

I looked at several of the issues (specifically #2275 and #2241) but the suggestions were not able to fix my problem. Running curl on my server (host, not container) results in the following:

curl https://some.server.com/v2/_catalog -> list of images

curl https://some.server.com:12443/v2/_catalog -> list of images

curl https://some.server.com/v2/webhooks/events -> 404 not found.

curl https://some.server.com:12443/v2/webhooks/events -> 404 not found.

So I'm not quite sure what's going with my configuration and any help would be appreciated!

megamaced commented 3 years ago

this issue for me seemed to go away after I increased the timeout value to 1500ms

notifications: endpoints:

stale[bot] commented 2 years ago

Thanks for all your contributions! This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.