unknown directive "more_set_headers" in /etc/nginx/conf.d/registry.conf:30

[polym]

Ｉ used contrib/compose/ to build up my private registry, but something wrong occured in compose_nginx container. I search for this problem, and find HttpHeadersMoreModule. So maybe just FROM: nginx:1.7 is not enough. We should add module to nginx and compile it.

[stevvooe]

@polym You can use add_header with the "always" parameter after 1.7.5 in nginx. We are a little annoyed with nginx, as well, since this is an odd restriction. I've file #460 to cover this.

Let me know how you'd like to proceed.

[polym]

@stevvooe Thanks. I'm new to docker-registry, and try it by using document. :)

[macsteps]

Comment out or remove more_set_headers line, and add

add_header 'Docker-Distribution-Api-Version:' 'registry/2.0' always;

[kentoj]

I hit this same error today. Is there a fork with a PR to fix this yet?

[stevvooe]

@kentoj How do you propose we fix a bug in nginx with a fork of distribution?

[kentoj]

@stevvooe it looks like I must have misunderstood the issue. If @macsteps suggestion is not a solution to this problem then I don't know how to fix this.

[stevvooe]

@kentoj We need to get the documentation in order on this. @macsteps solution is the right approach but requires nginx 1.7.5+.

[thaJeztah]

@stevvooe for people using a containerised NGINX; 1.9 is now the only supported NGINX version on the registry; https://registry.hub.docker.com/_/nginx/

[stevvooe]

@thaJeztah Looks like we should move the documentation to fully embrace the add_headers directive. This will clean things up a bit. Thank you for the update.

cc @moxiegirl