# Installer docker-squash avec Homebrew

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de docker-squash pour les workflows d'agents IA.

## installation

```sh
sudo av install brew:docker-squash
```

Commandes d'installation supplémentaires:

### macOS

- Homebrew (100%):

```sh
brew install docker-squash
```

  Preuve: local Homebrew formula metadata

## Faits du paquet

- **Clé du paquet:** brew:docker-squash
- **Gestionnaire de paquets:** Homebrew
- **Version:** 1.2.2
- **Résumé source:** Docker image squashing tool
- **Page d'accueil:** <https://github.com/goldmann/docker-squash>
- **Dernière mise à jour:** 2026-05-21T10:31:32Z
- **Généré:** 2026-08-03T19:37:03+00:00

## exécutables

- docker-squash (alias)

## Comportement d'installation

- Bouteille: non disponible

## Version et fraîcheur

- page générée: 2026-08-03
- version du gestionnaire: 1.2.2
## Historique du projet et usages

docker-squash is a Python CLI for squashing Docker image layers. It grew out of a practical image-size problem: Dockerfile instructions create layers, temporary build artifacts can remain in earlier layers, and pushing, saving, or loading those images can cost unnecessary time and storage.

### Historique du projet

The README describes docker-squash as a tool that can squash the last n layers of an image or squash from a selected layer to the end, then load the result back into the Docker daemon or store it as a tar archive. It explicitly frames squashing as a way to organize images into more logical layers and avoid carrying temporary files.

### Historique d'adoption

The project was packaged for installation from source, PyPI, and Homebrew. Its relevance is strongest in the legacy Docker builder era, before BuildKit and multi-stage builds reduced the need for post-processing images to remove build-time artifacts.

### Modes d'utilisation

A typical command selects an image, optionally sets --from-layer or a number of layers, tags the new image with --tag, writes an archive with --output-path, or controls whether the result is loaded back into Docker. The README examples compare docker history before and after squashing to show layer changes.

### Pourquoi les passionnés de paquets s'y intéressent

docker-squash is notable because it packages image-layer surgery as a normal CLI command. It is a useful historical artifact for understanding how Docker users handled layer bloat before modern Dockerfile patterns and BuildKit made the problem less central.

### Chronologie

- Docker 1.9 era: The README documents Docker 1.9 or newer support.
- Python 3 era: The README documents Python 3.6 and newer support.
- BuildKit era: Docker documents the legacy Linux image builder as deprecated, making squashing tools more historical and niche.

### Related projects

- Related projects include Docker Engine, Docker's legacy builder, BuildKit, multi-stage Dockerfiles, and the docker history command used to inspect image layers.

### Sources

- <https://github.com/goldmann/docker-squash#readme>
- <https://docs.docker.com/engine/deprecated/#legacy-builder-for-linux-images>


## Notes de sécurité

Aucun manifest local de gestion des secrets correspondant n'a été trouvé pour docker-squash. Les métadonnées de paquet Nucleus restent publiées ici afin que la couverture future dispose d'une URL stable.



## Combined YAML source

View the package source record on GitHub. [combined/docker-squash.yml](https://github.com/mxcl/pkgdb/blob/main/combined/docker-squash.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph