goharbor.io: server is not source-packageable (Docker-based build, multi-service runtime)

Aperta
  • Qualcosa non va?
#13,134 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
20/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Tranquilla
Stack tecnologico
angular, docker, go, helm, postgresql, redis
Ambito
backend, build-system, databases, devops

Direzione di ricerca

Read make/photon/Makefile and inspect the v2.14.4 offline and online installer artifacts first. Confirm that the server requires its multi-service Docker deployment and that no standalone binary path is available; done means preserving the decision not to add a server package and directing packaging work to the separate harbor-cli repository.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Summary

Same structural shape as #13131 (Neon DB). Harbor's server side cannot be source-packaged as a single pantry recipe.

Investigation

  • Upstream build (make/photon/Makefile): compiles every Go binary inside Docker (golang:1.26.3) and bakes them into Photon Linux container images. The Docker daemon is mandatory. No go build ./... path produces a runnable system.
  • Upstream releases (v2.14.4): only harbor-offline-installer-v2.14.4.tgz (~700 MB bundle of Docker images) and harbor-online-installer-v2.14.4.tgz (~12 KB script that pulls images). Zero standalone binaries published.
  • Runtime: harbor server is a multi-service stack — harbor-core + harbor-jobservice + harbor-portal (Angular) + harbor-registry + harbor-registryctl + harbor-trivy-adapter, plus PostgreSQL + Redis. Running harbor-core alone yields nothing useful to an end user.

Prior art — no distro source-builds harbor server

Distro Status
Homebrew core only harbor-cli (separate goharbor/harbor-cli repo). Cask harbor is an unrelated torrent app.
AUR only harbor-cli
nixpkgs only harbor-cli (pkgs/by-name/ha/harbor-cli/package.nix)
Debian nothing for goharbor

Harbor's official deployment model is Helm chart / Docker Compose. There is no end-user CLI for the server; it's a service stack.

Recommendation

Do not attempt to package the harbor server. This is consistent with the cockroachdb (#13122/#13123) and neon (#13131) precedents — projects where the upstream build chain is fundamentally container-orchestration-shaped and a single-binary pantry recipe doesn't map.

A separate follow-up PR will package harbor-cli (from the goharbor/harbor-cli repo) — a standard Go single-binary that every other distro packages. That is the user-facing tool worth having in pantry.

Lingua principale
C
Stelle
199
Fork
142
Merge medio
2h 33m
PR unite (30g)
145

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

  • Nessun Dockerfile né file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di pkgxdev/pantry

Tutte le issue di pkgxdev/pantry

Issue simili

Altre issue su C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.