gitea-registry
Skill4 starsChanged 5 months agoMITView on GitHub
Use when working with the Gitea container registry — OCI/Docker v2 API, push/pull images, multi-arch builds, package management via API, and configuration for supported package types.
In this repository74 other files it gives its agents.
- AGENTS.mdAGENTS.md
- atlasSkill
- cert-managerSkill
- cilium-gatewaySkill
- cilium-networkSkill
- cnpgSkill
- dragonflySkill
- external-dnsSkill
- external-secretsSkill
- flaggerSkill
- fluxSkill
- gitea-apiSkill
- gitea-runnerSkill
- giteaSkill
- gitea-teaSkill
- gitea-webhooksSkill
- harbor-apiSkill
- harbor-helmSkill
- harborSkill
- harbor-terraformSkill
- helm-chartSkill
- helm-opsSkill
- helmSkill
- higress-helmSkill
- higress-operatorSkill
- higressSkill
- kserve-helmSkill
- kserve-operatorSkill
- kserveSkill
- kubeflow-pipelinesSkill
- kubeflowSkill
- kubeflow-trainerSkill
- kubeflow-training-operatorSkill
- mariadb-helmSkill
- mariadb-operatorSkill
- mariadbSkill
- netbird-cliSkill
- netbird-operatorSkill
- netbird-serverSkill
- netbirdSkill
- netbird-terraformSkill
- nextcloud-apiSkill
- nextcloud-helmSkill
- nextcloudSkill
- nvidia-device-pluginSkill
- rook-ceph-operatorSkill
- rook-cephSkill
- rook-ceph-toolboxSkill
- sealed-secretsSkill
- stakater-reloaderSkill
- tailscaleSkill
- tailscale-talosSkill
- talosconfigSkill
- talosctlSkill
- talosSkill
- talos-terraformSkill
- tekton-operatorSkill
- tekton-pacSkill
- tekton-pipelinesSkill
- tektonSkill
- The first 60 shown.
The file
Files
Gitea Container Registry (v1.26)
OCI-compatible registry using Docker Registry API v2. Supports Docker images, Helm charts, and all OCI artifacts.
Auth
docker login git.example.com
# Username: gitea username
# Password: personal access token (NOT account password for 2FA users)Image Naming
{registry}/{owner}/{image}:{tag}Examples: git.example.com/testuser/myapp:latest, git.example.com/myorg/backend:v1.2.3
Push / Pull
docker tag myapp:latest git.example.com/testuser/myapp:latest
docker push git.example.com/testuser/myapp:latest
docker pull git.example.com/testuser/myapp:latestMulti-Arch
docker buildx build --platform linux/amd64,linux/arm64 \
-t git.example.com/testuser/myapp:latest --push .API
# List packages for owner
curl -H "Authorization: token <token>" \
https://git.example.com/api/v1/packages/testuser
# Delete package version
curl -X DELETE -H "Authorization: token <token>" \
https://git.example.com/api/v1/packages/testuser/container/myapp/1.0.0Supported Package Types
alpine, cargo, chef, composer, conan, conda, container, cran, debian, generic, go, helm, maven, npm, nuget, pub, pypi, rpm, rubygems, swift, vagrant, terraform (v1.26+).
Config
[packages]
ENABLED = true
LIMIT_SIZE_CONTAINER = -1 # No size limit for container imagesCommon Mistakes
- Tag case — Tags are case-insensitive.
image:Tagandimage:tagare the same image. - Auth for 2FA users — Always use a personal access token as password, not account password.
- Delete needs all segments — REST delete endpoint requires owner, type, name, and version.
- Helm chart push — Use
helm pushwith OCI format:helm push mychart-1.0.0.tgz oci://git.example.com/myorg.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

