Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add docs section for sub-paths with the container registry #27505

Merged
merged 3 commits into from
Oct 9, 2023
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions docs/content/usage/packages/container.en-us.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,23 @@ The container registry follows the OCI specs and supports all compatible images
To work with the Container registry, you can use the tools for your specific image type.
The following examples use the `docker` client.

### Reverse Proxy / URL Prefix
KN4CK3R marked this conversation as resolved.
Show resolved Hide resolved

The container registry uses a fixed url path `/v2` which can't be changed.
Even if you deploy Gitea with a prefix, `/v2` will be used by the `docker` client.
Therefore you may need to add an additional route to your reverse proxy configuration.

Example using nginx:
```
KN4CK3R marked this conversation as resolved.
Show resolved Hide resolved
location /gitea/ { ## normal Gitea route
proxy_pass http://gitea:3000/;
KN4CK3R marked this conversation as resolved.
Show resolved Hide resolved
}

location /v2/ { ## Gitea Docker Registry route
proxy_pass http://gitea:3000/v2/;
}
```

## Login to the container registry

To push an image or if the image is in a private registry, you have to authenticate:
Expand Down
Loading