Penyelesaian otomatis paket menggunakan apt dalam container Docker Debian atau Ubuntu – Beragampengetahuan
Pelengkapan otomatis paket tidak berfungsi di wadah Docker setelah build dasar, bahkan jika Anda telah menginstalnya bash-completion.menonaktifkan cache paket untuk menghemat ruang, karena diasumsikan bahwa Anda menentukan paket yang tersedia selama pembangunan dan tidak menggunakannya nanti apt atau apt-get.
Namun, jika Anda ingin pelengkapan otomatis paket, Anda harus memodifikasi file
/etc/apt/apt.conf.d/docker-cleanContents
Berkas asli
# Since for most Docker users, package installs happen in "docker build" steps,
# they essentially become individual layers due to the way Docker handles
# layering, especially using CoW filesystems. What this means for us is that
# the caches that APT keeps end up just wasting space in those layers, making
# our layers unnecessarily large (especially since we'll normally never use
# these caches again and will instead just "docker build" again and make a brand
# new image).
# Ideally, these would just be invoking "apt-get clean", but in our testing,
# that ended up being cyclic and we got stuck on APT's lock, so we get this fun
# creation that's essentially just "apt-get clean".
DPkg::Post-Invoke { "rm -f /var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb /var/cache/apt/*.bin || true"; };
APT::Update::Post-Invoke { "rm -f /var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb /var/cache/apt/*.bin || true"; };
Dir::Cache::pkgcache "";
Dir::Cache::srcpkgcache "";
# Note that we do realize this isn't the ideal way to do this, and are always
# open to better suggestions (
mengomentari tiga baris pertama
# Since for most Docker users, package installs happen in "docker build" steps,
# they essentially become individual layers due to the way Docker handles
# layering, especially using CoW filesystems. What this means for us is that
# the caches that APT keeps end up just wasting space in those layers, making
# our layers unnecessarily large (especially since we'll normally never use
# these caches again and will instead just "docker build" again and make a brand
# new image).
# Ideally, these would just be invoking "apt-get clean", but in our testing,
# that ended up being cyclic and we got stuck on APT's lock, so we get this fun
# creation that's essentially just "apt-get clean".
#DPkg::Post-Invoke { "rm -f /var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb /var/cache/apt/*.bin || true"; };
#APT::Update::Post-Invoke { "rm -f /var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb /var/cache/apt/*.bin || true"; };
#Dir::Cache::pkgcache "";
Dir::Cache::srcpkgcache "";
# Note that we do realize this isn't the ideal way to do this, and are always
# open to better suggestions (
lalu jalankan lagi
Semuanya sudah siap!
Pengusaha | Full Stack Developer | Pendiri MediSign Ltd. Saya memiliki lebih dari 15 tahun pengalaman profesional merancang dan mengembangkan aplikasi web. Saya juga sangat berpengalaman dalam mengelola proyek (web).
rencana pengembangan website
metode pengembangan website
jelaskan beberapa rencana untuk pengembangan website, proses pengembangan website, kekuatan dan kelemahan bisnis pengembangan website
, jasa pengembangan website, tahap pengembangan website, biaya pengembangan website
#Penyelesaian #otomatis #paket #menggunakan #apt #dalam #container #Docker #Debian #atau #Ubuntu
