Skip to content
This repository was archived by the owner on Apr 17, 2023. It is now read-only.

couldn't delete tag from registry by portus #1402

Closed
dnull88 opened this issue Aug 31, 2017 · 3 comments
Closed

couldn't delete tag from registry by portus #1402

dnull88 opened this issue Aug 31, 2017 · 3 comments

Comments

@dnull88
Copy link

dnull88 commented Aug 31, 2017

i try use portus on kubernetes (minikube). DB,Registry,portus is up. Authentication (as docker login) works, webhook-notification works. When i try delete tag by portus - i receive "... unable to be removed." In registry log:
time="2017-08-31T21:09:10.144423169Z" level=warning msg="error authorizing context: authorization token required" go.version=go1.7.6 http.request.host="reg.****.ua:5000" http.request.id=f71aec65-a4e9-4699-9a26-9279109f9614 http.request.method=DELETE http.request.remoteaddr="172.17.0.1:33880" http.request.uri="/v2/dnull/busybox/manifests/sha256:8573b4a813d7b90ef3876c6bec33db1272c02f0f90c406b25a5f9729169548ac" http.request.useragent=Ruby instance.id=01020c26-6db1-4ab5-8376-f2e65c90f9b4 service=registry vars.name="dnull/busybox" vars.reference="sha256:8573b4a813d7b90ef3876c6bec33db1272c02f0f90c406b25a5f9729169548ac" version=v2.6.2 172.17.0.1 - - [31/Aug/2017:21:09:10 +0000] "DELETE /v2/dnull/busybox/manifests/sha256:8573b4a813d7b90ef3876c6bec33db1272c02f0f90c406b25a5f9729169548ac HTTP/1.1" 401 153 "" "Ruby"

Portus log: 
Started DELETE "/tags/1.json" for 172.17.0.1 at 2017-08-31 21:11:46 +0000
Processing by TagsController#destroy as JSON
  Parameters: {"id"=>"1", "tag"=>{}}
Could not delete tag on the registry: execution expired
Completed 500 Internal Server Error in 2025ms (ActiveRecord: 4.7ms)

delete enabled in registry and portus. Registry version - 2.6, Portus version - 2.3.0-dev
Same configuration works on docker-compose (with same envs,certs,images).
Maybe someone can help with this problem?

@mssola
Copy link
Collaborator

mssola commented Sep 1, 2017

Here's your problem: Could not delete tag on the registry: execution expired. In the source code of Portus we have a timeout of 2 seconds for any HTTP request, which includes the registry (see this line). So, I'd start investigating why is it so slow (if you could login with docker, then I assume that the registry is reachable at some point).

@mssola
Copy link
Collaborator

mssola commented Sep 1, 2017

It's also worth mentioning that this timeout value is quite magical (at the time we thought it was enough, but maybe this isn't always the case). So another solution would be to increase it (or even make it configurable). That being said, I'd like to know why is it so slow...

Would it be possible for you to increase this value, and check which is the timeout value that works for you ?

@mssola
Copy link
Collaborator

mssola commented Feb 2, 2018

Closing due to inactivity. I believe that we have polished this feature quite a lot. Otherwise, there's an issue (#1599) that might relate a bit with these kinds of issues.

@mssola mssola closed this as completed Feb 2, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants