Federico Gimenez

@SezBulent thanks for raising this issue, It is very interesting that you get the 401 on a GET request, which is the only cached method when `ALLOW_PUSH` is set to...

I've been able to reproduce trying to push an image with several big layers (above 500Mb), it starts retrying them and I finally get an EOF. I get these messages...

Looks like in my case the problem is related to this location directive https://github.com/rpardini/docker-registry-proxy/blob/master/nginx.conf#L279-L283 with it in place the `proxy_read_timeout` setting in the server block is completely ignored and I...

@SezBulent you are right, commenting out https://github.com/rpardini/docker-registry-proxy/blob/master/nginx.conf#L279-L283 in fact didn't help, the successful executions I got were just bc the uploads happened to last less than 60s. Will keep trying...

Awesome, thanks a lot, for the record i also tried increasing `open_file_cache_valid`, the only remaining setting which default value is 60s, no luck. And very interesting to know that the...

@SezBulent awesome! looking forward to your PR, i've tried adding ``` proxy_connect_connect_timeout 1800s; proxy_connect_read_timeout 1800s; proxy_connect_send_timeout 1800s; ``` to the _director server block and I get a consistent 95s connect...

I'm still getting the same timeouts with 0.6.2 trying to push big layers, for instance with an image like this: ``` FROM alpine RUN head -c 1073741824 file.txt RUN head...

> I'm still getting the same timeouts with 0.6.2 trying to push big layers Setting higher values for timeouts through the env vars all is working fine :+1:

Running gazelle with go as explained here works for me https://github.com/bazelbuild/bazel-gazelle#running-gazelle-with-go

Thanks a lot for the pointer @skymeyer! We didn't have a `go_repository` referencing `com_github_bazelbuild_buildtools` but did have a `http_archive` getting it and we were later loading `buildifier_dependencies`. In fact we...