Docker build seems to overweighted and not performant for storage/build

Aperta
  • Qualcosa non va?
#2,666 1 commento 6 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
docker, go
Ambito
build-system

Direzione di ricerca

The issue does not identify files, tests, or an implementation entry point. Start by reading the project’s Docker build and cache documentation, then locate the container build path and its tests. The requested outcome is smaller, faster OCI image builds with better cache reuse, but the issue does not define measurable acceptance criteria.

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

Descrizione

feature looks hard p3 processed triage
What problem are you trying to solve?

Im in love with this proyect, seems it fixed a problem i didn't know i had but is one of the best solutions I've found. The only problem i've found is trying to use this for pipelines and oci containers. They are veeeeery slow to generate, even when i dont have that many packages, and they are very bulky

What solution would you like?

i dont know how to reduce the size, but i would love it to at least be more efficient when building and rehusing cache. so i've found a similar proyect that is called flox, which seems better at doing this. instead of generating a single docker layer, it generates one layer per package, that in many cases helps a lot when reinstalling and pushing to regisitries, because it has the same hash layer. Also it can therefore also skip reinstalling packages with the same previos version. Flox attempts to solve same issues as here, but the usability of devbox and the similarity to node packages.json is much more readeable and efficient to write and to help new users to be confortable with devbox. what do you think?

Alternatives you've considered

No response

Lingua principale
Go
Stelle
12.4k
Fork
358
Merge medio
17h 12m
PR unite (30g)
31

Preparare l'ambiente

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 jetify-com/devbox

Tutte le issue di jetify-com/devbox

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.