official-images
jib
Our great sponsors
official-images | jib | |
---|---|---|
14 | 46 | |
6,271 | 13,390 | |
1.7% | 0.9% | |
10.0 | 8.0 | |
2 days ago | 4 days ago | |
Shell | Java | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
official-images
-
Nix is a better Docker image builder than Docker's image builder
Ubuntu now has snapshot.ubuntu.com, see https://ubuntu.com/blog/ubuntu-snapshots-on-azure-ensuring-p...
Related discussion about reproducible builds by the Docker people: https://github.com/docker-library/official-images/issues/160...
- Starter for Jakarta EE staged (beta)
-
How to own your own Docker Registry address
> In their updated policy, it appears they now won't remove any existing images, but projects who don't pay up will not be able to publish any new images
This is not correct. It's the "organization" features are going away. That is the feature which lets you create teams, add other users to those teams, and grant teams access to push images and access private repositories. Multiple maintainers can still collaborate on publishing new images through use of access tokens which grant access to publish those images. It's kind of a hack, but it works. You would typically use these access tokens with automated CI tools anyway. This will require converting the organization account to a personal user (non-org) account. (Interesting note/disclosure: I was the engineer who first implemented the feature of converting a personal user account into an organization account some time around 2014/2015, but I no longer work there.)
For open source projects which are not part of the Docker Official Images (the "library" images [1]), they announced that such projects can apply to the Docker-Sponsored Open Source Program [2].
I would also heed the warning from the author of this article:
> Self-hosting a registry is not free, and it's more work than it sounds: it's a proper piece of infrastructure, and comes with all the obligations that implies, from monitoring to promptly applying security updates to load & disk-space management. Nobody (let alone tiny projects like these) wants this job.
Having most container images hosted by a handful of centralized registries has its problems, as noted, but so does an alternative scenario where multiple projects which decided to go self-hosted eventually lack the resources to continue doing so for their legacy users. Though, I suppose the nice thing about container images is that you can always pull and push them somewhere else to keep around indefinitely.
[1] https://hub.docker.com/u/library
-
Docker's deleting Open Source images and here's what you need to know
Indeed. While I do maintain two of them, that maintenance is effectively equivalent to being an open source maintainer or open source contributor. I do not have any non-public knowledge about the Docker Official Images program. My interaction with the Docker Official Images program can be summed up as “my PRs to docker-library/official-images” (https://github.com/docker-library/official-images/pulls/TimW...) and the #docker-library IRC channel on Libera.Chat.
-
Oracle per-employee Java pricing causes concern
"AdoptOpenJDK up until now was producing OpenJDK binaries with both Hotspot and OpenJ9 VM's. With Adopt's move to Eclipse, legal restrictions prevent the new Eclipse Adoptium group from producing/releasing OpenJ9 based binaries. As a result, IBM will be producing OpenJ9 based binaries in 2 flavours, Open and Certified, both under the family name IBM Semeru Runtimes. Essentially the same binaries, released under different licenses."
Source: https://github.com/docker-library/official-images/pull/10666...
-
PHP 8.2.0 has been released!
They should be available soon, the corresponding PR at docker-library/official-images has already been merged: https://github.com/docker-library/official-images/pull/13693
-
Docker series (Part 8): Images from Docker Hub
Official image lists are added here: https://github.com/docker-library/official-images/tree/master/library
-
GCC 12.1 Released
Looks like this PR will release the official version to the hub: https://github.com/docker-library/official-images/pull/12382
-
1 Million Docker pulls and more container updates
We’ve also officially release containers for ppc64le available on all the major registries and we’ve also gone ahead and updated our containers to 8.5.4 and patched against the latest security updates where applicable. 18 packages have been updated and you can see that work here.
- Where are the 10.7.2/10.7.3 docker images?
jib
- Nix is a better Docker image builder than Docker's image builder
-
Deploy Secure Spring Boot Microservices on Amazon EKS Using Terraform and Kubernetes
You need to build Docker images for each app. This is specific to the JHipster application used in this tutorial which uses Jib to build the images. Make sure you are logged into Docker using docker login. Navigate to each app folder (store, invoice, product) and run the following command:
-
Tool to build Docker images
JIB
-
Thin (ish) Clojure jars for better docker containers
It is pretty easy to do with https://github.com/GoogleContainerTools/jib.
-
Trying to spin up a Ktor app using docker containers. I keep getting "no main manifest attribute, in app.jar"
Save yourself the dockerfile and use jib: https://github.com/GoogleContainerTools/jib/tree/master/jib-maven-plugin
-
Fearless Distroless
I first learned about Distroless because it was the default option in Google's Jib. Jib is a Maven plugin to create Docker containers without dependency on Docker. Note that the default has changed now.
- Razvijanje mikroservisa na lokalnoj mrezi
-
Spring Boot pod takes 60 seconds to become ready; trouble handling spiky workloads
Optimize your Dockerfile by using a small base Java Image, use either Spring Boot's layers tools or Google Jib to build your docker file, and increase CPU/Memory requests and limits if you can.
-
CI/CD with Spring Boot and Jenkins Pipelines
In this section, we will setup the automated generation and deployment of a Docker container image. You will need a Docker Hub account and the Jib Gradle Plugin.
-
What is Docker All About and How to Deploy Spring Boot Application In Docker?
If you don't want to hack on your own scripts to package your app into a container, I can recommend the JIB maven plugin. A gradle version is also available.
What are some alternatives?
buildx - Docker CLI plugin for extended build capabilities with BuildKit
kaniko - Build Container Images In Kubernetes
gcc - Docker Official Image packaging for gcc
jkube - Build and Deploy java applications on Kubernetes
registry.k8s.io - This project is the repo for registry.k8s.io, the production OCI registry service for Kubernetes' container image artifacts
buildkit - concurrent, cache-efficient, and Dockerfile-agnostic builder toolkit
backend
Bazel - a fast, scalable, multi-language and extensible build system
nerdctl - contaiNERD CTL - Docker-compatible CLI for containerd, with support for Compose, Rootless, eStargz, OCIcrypt, IPFS, ...
docker-maven-plugin - INACTIVE: A maven plugin for Docker
4.2BSD - Upload of the source of 4.2BSD taken from /usr/src
shadow - Gradle plugin to create fat/uber JARs, apply file transforms, and relocate packages for applications and libraries. Gradle version of Maven's Shade plugin.