160% Year-over-Year Growth in Pulls of Red Hat’s Universal Base Image on Docker Hub

Red Hat’s Universal Base Image eliminates “works on my machine” headaches for developers.

It’s Red Hat Summit week, and we wanted to use this as an opportunity to highlight several aspects of Docker’s partnership with Red Hat. In this post, we highlight Docker Hub and Red Hat’s Universal Base Images (UBI). Also check out our new post on simplifying Kubernetes development with Docker Desktop + Red Hat OpenShift.

Docker Hub is the world’s largest public registry of artifacts for developers, providing the fundamental building blocks — web servers, runtimes, databases, and more — for any application. It offers more than 15 million images for containers, serverless functions, and Wasm with support for multiple operating systems (Linux, Windows) and architectures (x86, ARM). Altogether, these 15 million images are pulled more than 16 billion times per month by over 20 million IPs.

While the majority of the 15 million images are community images, a subset are trusted content, both open source and commercial, curated and actively maintained by Docker and upstream open source communities and Docker’s ISV partners.

Docker and Red Hat have been partners since 2013, and Red Hat started distributing Linux images through Docker Hub in 2014. To help developers reduce the “works on my machine” finger-pointing and ensure consistency between development and production environments, in 2019 Red Hat launched Universal Base Image (UBI). Based on Red Hat Enterprise Linux (RHEL), UBI provides the same reliability, security, and performance as RHEL. Furthermore, to meet the different use cases of developers and ISVs, UBI comes in four sizes — standard, minimal, multi-service, and micro — and offers channels so that additional packages can be added as needed.

Given Docker’s reach in the developer community and the breadth and depth of developer content on Docker Hub, Docker and Red Hat agreed that distributing Red Hat UBI on Docker Hub made a lot of sense. Thus, in May 2021 Red Hat became a Docker Verified Publisher (DVP) and launched Red Hat UBIs on Docker Hub. As a DVP, Red Hat’s UBIs are easier for developers to discover, and it gives developers an extra level of assurance that the images they’re using are accessible, safe, and maintained.

The results? Tens of 1000s of developers are pulling Red Hat UBI millions of times every month. Furthermore, the pulls of Red Hat Universal Base image have grown 2.6X times in the last 12 months alone. Such growth points to value Docker and Red Hat together bring to the developer community.

… and we’re not finished! Having provided Red Hat UBIs directly to developers, now Docker and Red Hat are working together with Docker’s ISV partners and open source communities to bring the value of UBI to those software stacks as well. Stay tuned for more!

Learn More

Docker Verified Publisher (DVP)

Red Hat Universal Base Images (UBIs)

Docker Official Images (DOI)

Docker-sponsored Open Source (DSOS)

Quelle: https://blog.docker.com/feed/

Simplifying Kubernetes Development: Docker Desktop + Red Hat OpenShift

It’s Red Hat Summit week, and we wanted to use this as an opportunity to highlight several aspects of the Docker and Red Hat partnership. In this post, we highlight Docker Desktop and Red Hat OpenShift. In another post, we talk about 160% year-over-year growth in pulls of Red Hat’s Universal Base Image on Docker Hub.

Why Docker Desktop + Red Hat OpenShift?

Docker Desktop + Red Hat OpenShift allows the thousands of enterprises that depend on Red Hat OpenShift to leverage the Docker Desktop platform that more than 20 million active developers already know and trust to eliminate daily friction and empower them to deliver results.

What problem it solves

Sometimes, it feels like coding is easy compared to the sprint demo and getting everybody’s approval to move forward. Docker Desktop does the yak shaving to make developing, using, and testing containerized applications on Mac and Windows local environments easy, and the Red Hat OpenShift extension for Docker Desktop extends that with one-click pushes to Red Hat’s cloud container platform.

One especially convenient use of the Red Hat OpenShift extension for Docker Desktop is for quickly previewing or sharing work, where the ease of access and friction-free deploys without waiting for CI can reduce cycle times early in the dev process and enable rapid iteration leading up to full CI and production deployment.

Getting started

If you don’t already have Docker Desktop installed, refer to our guide on Getting Started with Docker.

Installing the extension

The Red Hat OpenShift extension is one of many in the Docker Extensions Marketplace. Select Install to install the extension.

👋 Pro tip: Have an idea for an extension that isn’t in the marketplace? Build your own and let us know about it! Or don’t tell us about it and keep it for internal use only — private plugins for company or team-specific workflows are also a thing.

Signing into the OpenShift cluster in the extension

From within your Red Hat OpenShift cluster web console, select the copy login command from the user menu:

👋 Don’t have an OpenShift cluster? Red Hat supports OpenShift exploration and development with a developer sandbox program that offers immediate access to a cluster, guided tutorials, and more. To sign up, go to their Developer Sandbox portal.

That leads to a page with the details you can use to fetch the Kubernetes context you can use in the Red Hat OpenShift extension and elsewhere:

From there, you can come back to the Red Hat OpenShift extension in Docker Desktop. In the Deploy to OpenShift screen, you can change or log in to a Kubernetes context. In the login screen, paste the whole oc login line, including the token and server URL from the previous:

Your first deploy

Using the extension is even easier than installing it; you just need a containerized app. A sample racing-game-app is ready to go with a Dockerfile (docs) and OpenShift manifest (docs), and it’s a joy to play.

To get started, clone https://github.com/container-demo/HexGL.

👋 Pro tip: Have an app you want to containerize? Docker’s newly introduced docker init command automates the creation of Dockerfiles, Compose manifests, and .dockerignore files.

Build your image

Using your local clone of sample racing-game-app, cd into the repo on your command line, where we’ll build the image:

docker build –platform linux/amd64 -t sample-racing-game .

The –platform linux/amd64 flag forces x86 compatible image, even if you’re building from a Mac with Apple Silicon/ARM CPU. The -t sample-racing-game names and tags your image with something more recognizable than a SHA256. Finally, the trailing dot (“.”) tells Docker to build from the current directory.

Starting with Docker version 23, docker build leverages BuildKit with more performance, better caching, and support for things like build secrets that make our lives as developers easier and more secure.

Test the image locally

Now that you’ve built your image, you can test it out locally. Just run the image using:

docker run -d -p 8080:8080 sample-racing-game

And open your browser to http://localhost:8080/ to take a look at the result.

Deploy to OpenShift

With the image built, it’s time to test it out on the cluster. We don’t even have to push it to a registry first.

Visit the Red Hat OpenShift extension in Docker Desktop, select our new sample-racing-game image, and select Push to OpenShift and Deploy from the action button pulldown:

The Push to OpenShift and Deploy action will push the image to the OpenShift cluster’s internal private registry without any need to push to another registry first. It’s not a substitute for a private registry, but it’s convenient for iterative development where you don’t plan on keeping the iterative builds.

Once you click the button, the extension will do exactly as you intend and keep you updated about progress:

Finally, the extension will display the URL for the app and attempt to open your default browser to show it off:

Cleanup

Once you’re done with your app, or before attempting to redeploy it, use the web terminal to all traces of your deployment using this one-liner:

oc get all -oname | grep sample-racing-game | xargs oc delete

That will avoid unnecessarily using resources and any errors if you try to redeploy to the same namespace later.

So…what did we learn?

The Red Hat OpenShift extension gives you a one-click deploy from Docker Desktop to an OpenShift cluster. It’s especially convenient for previewing iterative work in a shared cluster for sprint demos and approval as a way to accelerate iteration.

The above steps showed you how to install and configure the extension, build an image, and deploy it to the cluster with a minimum of clicks. Now show us what you’ll build next with Docker and Red Hat, tag @docker on Twitter or me @misterbisson@techub.social to share!

Learn More

Learn how to build and share a containerized app

Integrating Docker with your IDE

AI and ML with Docker

Connect with Docker

Roadmap

Forums

Slack

Quelle: https://blog.docker.com/feed/

Amazon Rekognition führt die Erkennung von Gesichtsverdeckungen ein, um die Genauigkeit der Identitätsprüfung zu verbessern

Heute kündigte AWS die allgemeine Verfügbarkeit der Erkennung von Gesichtsverdeckungen an, um die Genauigkeit der Gesichtsverifizierung zu verbessern. Das neue FaceOccluded-Attribut in den DetectFaces- und IndexFaces-APIs von Amazon Rekognition erkennt, ob das Gesicht in einem Bild teilweise erfasst oder aufgrund von überlappenden Objekten, Kleidung und Körperteilen nicht vollständig sichtbar ist.
Quelle: aws.amazon.com

Amazon QuickSight unterstützt jetzt Statuspersistenz und Lesezeichen für eingebettete Dashboards

Amazon QuickSight unterstützt jetzt Statuspersistenz für eingebettete Dashboards (und Konsolen) für registrierte Benutzer. Eingebettete QuickSight-Dashboards speichern jetzt die Filterauswahl zwischen Besuchen, wenn sie als registrierter QuickSight-Benutzer aufgerufen werden. Registrierte Benutzer können auch bestimmte Ansichten des eingebetteten Dashboards mit einem Lesezeichen versehen, sodass Sie ganz einfach von einem zentralen Ort aus auf Ihre Einstellungen zugreifen können. Sie können beispielsweise ein Lesezeichen für ein eingebettetes Dashboard mit einer bestimmten Filtereinstellung erstellen, die sich vom ursprünglichen Dashboard unterscheidet. Auf diese Weise können Sie schnell zwischen den relevanten Ansichten wechseln, ohne die Filter erneut initialisieren zu müssen. Sie können Lesezeichen und Statuspersistenz über die GenerateEmbedUrlForRegisteredUser-API aktivieren. Weitere Informationen finden Sie in unserer Dokumentation.
Quelle: aws.amazon.com

AWS Backup unterstützt regionsübergreifende Backups in vier neuen Regionen

Heute kündigen wir Unterstützung von regionsübergreifenden Backups für die Regionen Asien-Pazifik (Hyderabad), Asien-Pazifik (Melbourne), Europa (Spanien) und Europa (Zürich) an. Mit regionsübergreifenden Backups können Sie ein Exemplar Ihrer Backup-Daten in anderen AWS-Regionen als dem Speicherort Ihrer primären Backups speichern und so die Anforderungen an Geschäftskontinuität, Notfallwiederherstellung und Compliance erfüllen. AWS Backup ist ein vollständig verwalteter, richtliniengesteuerter Service, der die zentrale Automatisierung des Datenschutzes auf mehreren AWS-Services wie Computing, Speicher und Datenbank ermöglicht. Mit AWS Backup können Sie unveränderliche Backups für Ihre Anwendungsdaten zentral erstellen und verwalten, Ihre Daten vor versehentlichen oder böswilligen Aktionen schützen und die Daten mit wenigen Mausklicks wiederherstellen.
Quelle: aws.amazon.com