Hi there! I'm Maneshwar. Right now, I’m building LiveAPI, a first-of-its-kind tool that helps you automatically index API endpoints across all your repositories. LiveAPI makes it easier to discover, understand, and interact with APIs in l…

Sichere Programmierung dev.to 24.07.2025, 19:01 Uhr 3 Min. Lesezeit Cloud & IT-Enterprise

↗ Quelle (dev.to)

Reagiere als Erste:r — dein Feedback zählt!

Hi there! I'm Maneshwar. Right now, I’m building LiveAPI, a first-of-its-kind tool that helps you automatically index API endpoints across all your repositories. LiveAPI makes it easier to discover, understand, and interact with APIs in large infrastructures.

With modern Docker tooling, docker buildx is the preferred way to unlock advanced build features powered by BuildKit.

If you're still relying on classic docker build, you're missing out on faster builds, better caching, and powerful features like multi-arch images and inline secrets.

Let's break it down.

What is `docker buildx`?

docker buildx is a CLI plugin that extends the docker build command with BuildKit, a modern builder engine developed by Docker. It gives you access to:

Faster builds

Layer caching

Parallelization

Multi-platform support (e.g. linux/arm64, linux/amd64)

Better control over builder instances

Disk usage management

Getting Started

First, make sure you're using Docker with BuildKit enabled.

Add this to your shell config or export directly:

export DOCKER_BUILDKIT=1

export BUILDX_EXPERIMENTAL=1

Common `docker buildx` Commands

Here are the core commands you'll use:

`build`

The bread and butter. Like docker build, but better.

docker buildx build --platform linux/amd64,linux/arm64 -t myimage:latest .

Use --push to push directly to registry after build:

docker buildx build --platform linux/amd64,linux/arm64 -t user/myimage:latest --push .

`bake`

Declarative builds via docker-bake.hcl or docker-compose.yml.

docker buildx bake

Great for managing multiple targets/images in one shot.

Builder Instances

`create`

Set up an isolated builder environment:

docker buildx create --name mybuilder --use

This creates and uses mybuilder. You can now build multi-platform images and share cache state.

`inspect`

Check details:

docker buildx inspect --bootstrap

`ls`

List all your builders:

docker buildx ls

`prune`

Free up disk space:

docker buildx prune

Registry Tools

docker buildx imagetools helps inspect and work with multi-arch images stored in a registry:

docker buildx imagetools inspect user/myimage:latest

♂️ Debug & Experimental Mode

Enable debug logging:

docker buildx --debug build ...

To unlock hidden experimental features:

export BUILDX_EXPERIMENTAL=1

Other Useful Commands

Command	Description
`du`	Check build cache disk usage
`rm`	Remove builder instances
`stop`	Stop a running builder
`version`	Print version info of Buildx
`history`	Work with previous build records

Summary

If you're building Docker images in 2025 and not using buildx, you're leaving performance and control on the table.

Key benefits:

Multi-arch builds

Smart caching

Cleaner build management

Better registry tooling

Quick Setup for Daily Use

docker buildx create --use --name devbuilder

docker buildx build --platform linux/amd64,linux/arm64 -t youruser/yourapp:tag --push .

Done. You’ve now entered the world of modern Docker builds. 🐳

LiveAPI helps you get all your backend APIs documented in a few minutes.

With LiveAPI, you can generate interactive API docs that allow users to search and execute endpoints directly from the browser.

If you're tired of updating Swagger manually or syncing Postman collections, give it a shot.

CTI Threat Relationship Graph2 Knoten / 1 Relationen

CVE / Incident Software MITRE ATT&CK CWE Weakness IoC

IR-PLAYBOOK-VULN-REMEDIATIONMEDIUM

Schritte anzeigen

SOC Incident Playbook: Vulnerability Remediation & Verification

Asset Inventory

Asset-Datenbank nach betroffenen Komponenten, Versionen und exposed Ports abfragen.

nmap -sV --script vuln -p- <target-network>

Exploit MonitoringSofort

SIEM-Regeln und IDS-Signaturen (Snort/Suricata) auf Angriffsversuche schärfen.

tail -f /var/log/suricata/fast.log | grep <cve>

Patch DeploymentSofort

Patch oder offiziellen Workaround gemäß Hersteller-Empfehlung einspielen.

Check Vendor Security Advisory Bulletin

1-Click Detection Engineering: Multi-Dialect SIEM Rules5 Formate

Regeln anzeigen

Syntax validiert (0 Fehler)

title: Detect Exploitation - Understanding Docker Buildx & Builder: Modern Docker Builds with BuildKit
id: 9bb783ef-9a92-4ec8-834c-1fad4faf7b43
status: experimental
description: Automatisch generierte SIEM-Erkennungsregel basierend auf CTI Intelligence
references:
  - https://tsecurity.de/
author: iShareStuff CTI Automated Detection Engine
date: 2026-09-24
logsource:
  category: network_connection
  product: any
detection:
  selection:
      CommandLine|contains:
        - 'exploit'
  condition: selection
falsepositives:
  - Legitime administrative Zugriffe oder Penetrationstests
level: high
tags:
  - attack.initial_access

Syntax validiert (0 Fehler)

rule CTI_Threat_Indicator {
    meta:
        author = "iShareStuff CTI Automated Detection Engine"
        date = "2026-09-24"
        description = "YARA Signature for "
    strings:
        $str = "Understanding Docker Buildx & " ascii wide
    condition:
        any of them
}

Syntax validiert (0 Fehler)

index=security sourcetype IN ("cisco:asa", "pan:traffic", "zeek_conn", "suricata", "WinEventLog:Security")
("Understanding Docker Buildx  Builder Mod")
| stats count earliest(_time) as first_seen latest(_time) as last_seen by src_ip, dest_ip, dest_host, signature
| eval first_seen=strftime(first_seen, "%Y-%m-%d %H:%M:%S"), last_seen=strftime(last_seen, "%Y-%m-%d %H:%M:%S")
| sort - count

Syntax validiert (0 Fehler)

message: "*Understanding Docker Buildx  Builder Mod*"

Syntax validiert (0 Fehler)

CommonSecurityLog
| where Message has "Understanding Docker Buildx  Builder Mod"
| summarize EventCount = count(), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated) by SourceIP, DestinationIP, DestinationPort, Activity
| extend DetectionRule = "iShareStuff-CTI-Compiled"
| sort by EventCount desc

🎯

MITRE ATT&CK Matrix Navigator 14 Taktiken

Reconnaissance

Resource Development

Initial Access

Execution

Persistence

Privilege Escalation

Defense Evasion

Credential Access

Discovery

Lateral Movement

Collection

Command and Control

Exfiltration

Impact

💡 Tipp: Klicken Sie auf eine TTP, um Gegenmaßnahmen und SIEM-Erkennungsregeln anzuzeigen.Enterprise Matrix v14.1

🚀 Auf tsecurity.de entdecken

◀ VORHERIGER BEITRAG 2 Min

Apple Umeda Store Opens in Osaka with Focus on Accessibility and Local Culture

Apple iOS & macOS

NÄCHSTER BEITRAG 1 Min

I switched to a $280 Chromebook from my Windows laptop for a week - and didn't regret it

IT NachrichtenWeiterlesen ▶

Blättern: Pfeiltasten [ ← ] [ → ] · Tasten j / k · mobil: Wischen

Fokus-Vektor:

Kognitive Analyse für identifizierte Bedrohung: Erhöhte Bedrohungslage im Bereich Understanding Docker Buildx & Builder: M.... Basierend auf 368k Vektor-Korrelationen werden sofortige Isolationsmaßnahmen für betroffene Endpunkte empfohlen.

🛡️ Angriffsfläche & Exposure

Netzwerk/Remote-Zugriff ohne Vorauthentifizierung möglich.

⚡ Empfohlene Sofortmaßnahmen

1. Perimeter-Inspektion: Relevante Portfreigaben und exponierte Endpunkte unverzüglich scannen.
2. Patch-Applikation: Hersteller-Hotfix einspielen oder betroffene Daemons in isolierte DMZ-Segmente überführen.
3. Telemetrie & EDR-Alerts: Prozessaufrufe und Child-Processes auf anomale Shell-Spawns überwachen.

🔗 Semantisch verwandte Zero-Days MariaDB 11.7 VEC

Schnell-Prompts für Analysten

⚠️ DEFANGED SANDBOX VIEW (tsecurity.de): Alle Netzwerkindikatoren und URLs wurden neutralisiert (2 Indikatoren entschärft). Nur zur defensiven Analyse!

Format: python

#!/usr/bin/env python3
# Exploit Title: PoC for Target
import socket, sys
target = '192[.]168[.]1[.]10'
url = 'hxxp://target[.]local/vuln'
s = socket.socket()
s.connect((target, 80))
s.send(b'GET / HTTP/1.1\r\nHost: target.local\r\n\r\n')