#dockerhub

@michabbb.bsky.social

2 months ago

GitHub - michabbb/docker-security-scanner Contribute to michabbb/docker-security-scanner development by creating an account on GitHub.

🚀 Available on #DockerHub: michabbb/security-scanner

🔗 github.com/michabbb/do...

0 0 0 0

Shoper Gamer

@shopergamer.bsky.social

2 months ago

Docker Registry คืออะไร

อ่านต่อ : www.blockdit.com/posts/69423d...

#ShoperGamer #Docker #Study #DockerRegistry #Dockerhub #PublicRegistry #PrivateRegistry #Knowledge #Feed

2 0 0 0

Pure Tech

@puretech.news

3 months ago

Over 10,000 Docker Hub Images Found Leaking Credentials, Auth Keys joshuark shares a report from BleepingComputer: More than 10,000 Docker Hub container images expose data that should be protected, including live credentials to production systems, CI/CD databases, or...

Over 10,000 Docker Hub Images Found Leaking Credentials, Auth Keys #Technology #Cybersecurity #DockerHub #DataLeak #CybersecurityThreats

0 0 0 0

International Business Times

@ibtimes.bsky.social

3 months ago

A major security vulnerability has surfaced in the container world, directly impacting Docker Hub users.
#DockerHub #Leak

Read More: www.ibtimes.co.uk/docker-hub-i...

0 0 0 0

devXY

@devxy.bsky.social

3 months ago

devxygmbh/r-alpine - Docker Image Search Docker Hub

Decided to upkeep (Alpine) R images on #dockerhub instead of enforcing to use (self-hosted) #harbor registry.

hub.docker.com/r/devxygmbh/...

#devops #container #rstats

0 0 1 0

Fox Ritch (slow reply cause this is a mirror account)

@fjox.win

4 months ago

All my docker images are now on codeberg, github and docker hub!

#docker #container #dockerhub #codeberg #github

1 0 0 0

Molecular Oncology Almanac

@moalmanac.org

4 months ago

We just published a new minor release of our interpretation algorithm. Available on both #DockerHub and @github.com!
news.moalmanac.org/2025-10-24-a...

0 0 0 0

Pxl Phile

@ppxl.social.tchncs.de.ap.brid.gy

4 months ago

Status page from Docker Hub. It says: Full service disruption So nothing is working.

I heard docker was a disruptive technology 😂

#DockerHub

0 0 0 0

@hegerdes.bsky.social

5 months ago

How do you avoid the #DockerHub pull limit?
Just use the ionos pull through registry: `harbor.infra.cluster.ionos.com/docker.io`
No Limits, No Auth, No Guarantees

0 0 0 0

David Gardiner

@david.gardiner.net.au

5 months ago

Docker Systems Status Page The official status page for services offered by Docker.

FYI Docker Hub is experiencing an outage at the moment.

Attempting to pull images from hub.docker.com may fail. Seeing some builds fail with "401 Unauthorized"

www.dockerstatus.com

#Docker #DockerHub

1 0 0 0

CyberTaters

@potato.software

6 months ago

Mashers steal 3,325 secrets in #GhostAction #GitHub supply chain attack

www.bleepingcomputer.com/news/security/mashers-st...

#potatosecurity #PyPI #npm #DockerHub #Clownflare #AWS

1 0 0 0

Hackread.com

@hackread.bsky.social

6 months ago

GhostAction Attack Steals 3,325 Secrets from GitHub Projects Follow us on Bluesky, Twitter (X), Mastodon and Facebook at @Hackread

#GhostAction attack hit 817 GitHub repos, stealing 3,325 secrets including npm, PyPI, and DockerHub tokens.

Read: hackread.com/ghostaction-...

#CyberSecurity #GitHub #SupplyChain #PyPI #DockerHub #InfoSec

2 0 0 1

Apache Iggy (Incubating)

@iggy.rs

6 months ago

🚀 All Iggy core components are now on Docker Hub!
Server, Connectors, MCP, Web UI & Bench Dashboard — all in one place.

Run it in seconds: docker run apache/iggy

#iggy #apache #asf #docker #dockerhub #rust #mcp #streaming #messaging #connectors

4 3 0 0

ActiveState

@activestate.bsky.social

6 months ago

🔒 Free, minimal, secure containers—SBOMs & attestations included.

Find us on Docker Hub and build on a trusted foundation. buff.ly/yJv8Pjb

#ContainerSecurity #DockerHub #OpenSource

2 1 0 0

Status Is Down

@statusisdown.bsky.social

6 months ago

Is Docker down? [August 19, 2025] Docker is reportedly down for some users on August 19, 2025. Based on the graph showing on the outage tracking service DownDetector, the volume of user reports surged around 11:25AM Eastern Time. Soci...

Docker is reportedly down for some users right now. Are you one of them? #Docker #DockerHub #DockerDown

0 0 0 0

ActiveState

@activestate.bsky.social

7 months ago

Ready for secure containers with zero friction? ActiveState’s free images are always up-to-date, CVE-checked, and come with everything you need for secure deployments.

No sign-up, no hassle—just pull from DockerHub and go. buff.ly/yJv8Pjb

#ContainerSecurity #DockerHub

0 0 0 0

Vinicius Apolinario

@vrapolinario.bsky.social

10 months ago

After 2+ years since first published, I finally updated my Sample gMSA image to use #GitHubActions. The image is published to the #DockerHub and will be updated monthly!

Also, I added a tag for #WindowsServer 2025.

Check it out: hub.docker.com/r/vra...

#Docker #GitHub

0 0 0 0

Forem

@forem.com.web.brid.gy

10 months ago

Monitoring Docker Hub limits with Prometheus # The problem Once upon a time, Docker decided to spoil us all developers and operators and had unlimited access to Docker Hub. You could pull as many images, as many times as your heart desired without any constraint, so we got used to it and never really thought about how good of a deal was that. Unfortunately, free and unlimited almost never go hand to hand and the day came when Docker decided to impose limits to how much you can pull from the mothership. At this point (April 2025) the limits have changed twice and the current numbers can be found at https://docs.docker.com/docker-hub/usage/. Many of us just created users for those machines with heavy `docker pull` usage and for most of it, it was fine. Until eventually something breaks. We started using caches where possible, but in some cases, the need for direct access was still there and therefore the need to know how much more can we pull for now and if any account had run dry. # Prometheus + Alertmanager + Grafana If you've been operating services for the last decade, chances are you've meet these tools. For the uninitiated: 1. Prometheus is used to collect metrics of your systems over time. 2. Alertmanager Takes care of handling alerts and distributing them to the right receiver. 3. Grafana Is used to visualize metrics, logs, traces, and by the time you read this probably other things 😄 These tools are widely used by operations teams as the backbone for monitoring and alerting and are the de facto standard in my opinion. This is not a tutorial about these tools specifically but I will explain how to pull the data into the tools and configure dashboards and alerts. ## Prometheus exporters Now, how do we get these metrics you ask? Well, we need to use a Prometheus exporter. This one specifically: https://github.com/jadolg/dockerhub-pull-limit-exporter. Prometheus itself doesn't directly integrate with every service. Exporters are services that get information from other software/services and expose in a format that Prometheus understands. Once active, you can add the exporter as a target to your Prometheus server and it will start scraping metrics from it periodically. # Installing The best and fastest way in my opinion to deploy the exporter is using docker compose. In your server (that already has docker and docker compose available), create a directory to place the configuration: mkdir dockerhub-pull-limit-exporter cd dockerhub-pull-limit-exporter Download the example configuration wget -O config.yaml https://raw.githubusercontent.com/jadolg/dockerhub-pull-limit-exporter/refs/heads/main/config.example.yaml And replace the example credentials with yours. You can add as many accounts as your heart desires. You can also adjust the interval in which the exporter gets its information from DockerHub and the timeout for these requests. Once the configuration is in place, We need a docker compose file. services: dockerhub-pull-limit-exporter: image: ghcr.io/jadolg/dockerhub-pull-limit-exporter restart: unless-stopped ports: - 9101:9101 volumes: - ./config.yaml:/config.yaml Save it into the same directory and start the service: docker compose up -d # Prometheus And now it's time to setup Prometheus. There are many ways to do this since there are many ways to install Prometheus in the first place, but the general idea is the same. We need to add the exporter as a target to our Prometheus server so it knows what to scrape. Edit your Prometheus configuration and add the following target to your `scrape_configs` replacing **my-server** with your server's address: scrape_configs: - job_name: 'dockerhub_pull_limit_exporter' static_configs: - targets: ['my-server:9101'] After restarting Prometheus, the new metrics should available. # Grafana Now let's see what the metrics have to say. Head on to your Grafana and in the **Dashboards** section click **New/Import** : In the Import view use ID **23342** (created specifically for this exporter) and click Load and then Load (Weird choice of options, I know). If everything goes right and your metrics are available you should be greeted by a shinny new dashboard like mine: # Alerts Now we are collecting the data and we are able to see it but we need to get alerted when our limits are running low. In order to do that we need to add a new rule file to our Prometheus configuration: rule_files: - "alerts.dockerhub.rules.yml" And in that file we'll add the following alerts: groups: - name: DockerHubPullLimits rules: - alert: DockerHubPullsRemainingLow expr: dockerhub_pull_remaining_total/dockerhub_pull_limit_total * 100 < 10 for: 5m labels: severity: warning annotations: summary: "Account {{ $labels.account }} has used 90% of its pull limit" - alert: DockerHubPullsRemainingLowCritical expr: dockerhub_pull_remaining_total < 1 for: 5m labels: severity: critical annotations: summary: "Account {{ $labels.account }} has used 100% of its pull limit" Restart Prometheus and the alerts should be loaded. These alerts will be triggered when the accounts have used **90%** of the current limit and then when they have used **100%**. Next, configure Alertmanager to route this alert to your favorite notification channel and alerts will get to you when they trigger. # Final words Collecting metrics is an essential part of operating any software system. It's the window to your service's health and performance, and should be the main tool to use to diagnose when things go wrong. If there's a problem, there should be an alert for it and that alert should be based on metrics. With all this in place, the next time my services run out of docker pulls, I will know immediately, and if they are failing, I will have all the information I need to know if this is the cause. I will also have historical data which I'll be able to analyze to know what the trending usage is and be ready to improve my setup based on that data. And that's all for today folks! Happy monitoring! cover image: https://www.freepik.com/free-vector/switches-buttons-control-panel-vector-illustrations-set-retro-control-console-terminal-elements-dials-knobs-dashboard-system-monitor-display-technology-equipment-concept_28480839.htm

0 0 0 0

DEV Community

@dev.to.web.brid.gy

10 months ago

Monitoring Docker Hub limits with Prometheus # The problem Once upon a time, Docker decided to spoil us all developers and operators and had unlimited access to Docker Hub. You could pull as many images, as many times as your heart desired without any constraint, so we got used to it and never really thought about how good of a deal was that. Unfortunately, free and unlimited almost never go hand to hand and the day came when Docker decided to impose limits to how much you can pull from the mothership. At this point (April 2025) the limits have changed twice and the current numbers can be found at https://docs.docker.com/docker-hub/usage/. Many of us just created users for those machines with heavy `docker pull` usage and for most of it, it was fine. Until eventually something breaks. We started using caches where possible, but in some cases, the need for direct access was still there and therefore the need to know how much more can we pull for now and if any account had run dry. # Prometheus + Alertmanager + Grafana If you've been operating services for the last decade, chances are you've meet these tools. For the uninitiated: 1. Prometheus is used to collect metrics of your systems over time. 2. Alertmanager Takes care of handling alerts and distributing them to the right receiver. 3. Grafana Is used to visualize metrics, logs, traces, and by the time you read this probably other things 😄 These tools are widely used by operations teams as the backbone for monitoring and alerting and are the de facto standard in my opinion. This is not a tutorial about these tools specifically but I will explain how to pull the data into the tools and configure dashboards and alerts. ## Prometheus exporters Now, how do we get these metrics you ask? Well, we need to use a Prometheus exporter. This one specifically: https://github.com/jadolg/dockerhub-pull-limit-exporter. Prometheus itself doesn't directly integrate with every service. Exporters are services that get information from other software/services and expose in a format that Prometheus understands. Once active, you can add the exporter as a target to your Prometheus server and it will start scraping metrics from it periodically. # Installing The best and fastest way in my opinion to deploy the exporter is using docker compose. In your server (that already has docker and docker compose available), create a directory to place the configuration: mkdir dockerhub-pull-limit-exporter cd dockerhub-pull-limit-exporter Download the example configuration wget -O config.yaml https://raw.githubusercontent.com/jadolg/dockerhub-pull-limit-exporter/refs/heads/main/config.example.yaml And replace the example credentials with yours. You can add as many accounts as your heart desires. You can also adjust the interval in which the exporter gets its information from DockerHub and the timeout for these requests. Once the configuration is in place, We need a docker compose file. services: dockerhub-pull-limit-exporter: image: ghcr.io/jadolg/dockerhub-pull-limit-exporter restart: unless-stopped ports: - 9101:9101 volumes: - ./config.yaml:/config.yaml Save it into the same directory and start the service: docker compose up -d # Prometheus And now it's time to setup Prometheus. There are many ways to do this since there are many ways to install Prometheus in the first place, but the general idea is the same. We need to add the exporter as a target to our Prometheus server so it knows what to scrape. Edit your Prometheus configuration and add the following target to your `scrape_configs` replacing **my-server** with your server's address: scrape_configs: - job_name: 'dockerhub_pull_limit_exporter' static_configs: - targets: ['my-server:9101'] After restarting Prometheus, the new metrics should available. # Grafana Now let's see what the metrics have to say. Head on to your Grafana and in the **Dashboards** section click **New/Import** : In the Import view use ID **23342** (created specifically for this exporter) and click Load and then Load (Weird choice of options, I know). If everything goes right and your metrics are available you should be greeted by a shinny new dashboard like mine: # Alerts Now we are collecting the data and we are able to see it but we need to get alerted when our limits are running low. In order to do that we need to add a new rule file to our Prometheus configuration: rule_files: - "alerts.dockerhub.rules.yml" And in that file we'll add the following alerts: groups: - name: DockerHubPullLimits rules: - alert: DockerHubPullsRemainingLow expr: dockerhub_pull_remaining_total/dockerhub_pull_limit_total * 100 < 10 for: 5m labels: severity: warning annotations: summary: "Account {{ $labels.account }} has used 90% of its pull limit" - alert: DockerHubPullsRemainingLowCritical expr: dockerhub_pull_remaining_total < 1 for: 5m labels: severity: critical annotations: summary: "Account {{ $labels.account }} has used 100% of its pull limit" Restart Prometheus and the alerts should be loaded. These alerts will be triggered when the accounts have used **90%** of the current limit and then when they have used **100%**. Next, configure Alertmanager to route this alert to your favorite notification channel and alerts will get to you when they trigger. # Final words Collecting metrics is an essential part of operating any software system. It's the window to your service's health and performance, and should be the main tool to use to diagnose when things go wrong. If there's a problem, there should be an alert for it and that alert should be based on metrics. With all this in place, the next time my services run out of docker pulls, I will know immediately, and if they are failing, I will have all the information I need to know if this is the cause. I will also have historical data which I'll be able to analyze to know what the trending usage is and be ready to improve my setup based on that data. And that's all for today folks! Happy monitoring! cover image: https://www.freepik.com/free-vector/switches-buttons-control-panel-vector-illustrations-set-retro-control-console-terminal-elements-dials-knobs-dashboard-system-monitor-display-technology-equipment-concept_28480839.htm

0 0 0 0

Docker

@docker.com

10 months ago

Shipping software shouldn’t require caffeine, duct tape, and a prayer. 🙏

With Docker Hub, you get:
⚡️ Fast, reliable image access
✅ Trusted content that scales
🔐 Public and private repos
🤖 CI/CD integrations + webhooks
🧪 Automated builds & tests

#Docker #DockerHub #DevTools