Grocker - a Docker image builder for Python applications
Grocker allows you to bundle your Python applications as Docker image while keeping the image size as minimal as possible.
Grocker uses debian:buster, debian:bookworm or alpine:latest as its base image.
Grocker is hosted on Github at https://github.com/polyconseil/Grocker. Grocker full documentation is available on https://grocker.readthedocs.io/.
Installation
Install Docker Engine. See its official documentation.
Install Grocker with pip: pip install grocker.
Basic usage
$ grocker build ipython==5.0.0 --entrypoint ipython
$ docker run --rm -ti ipython:5.0.0-<grocker-version>Direct wheel path
A wheel can also be directly passed to grocker to avoid the need to upload an artefact to build an image.
Grocker will switch to this mode if a / is present in the argument. Pip extra requirements can be used in this mode.
$ grocker build ./path/to/ipython-7.1.1-py3-none-any.whl[doc] --entrypoint ipython
$ docker run --rm -ti ipython-doc:7.1.1-<grocker-version>5 maintainers
Metadata
5 maintainers
Release files for grocker 8.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| grocker-8.3.tar.gz | 18.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| grocker-8.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 42.3 kB
Release files / grocker-8.3.tar.gz
| Download URL | grocker-8.3.tar.gz |
|---|---|
| Size | 18.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
304f38ca2d192f6161f3221b868ad37cf85de6ad846ad97db86f56140d7fa7b9
|
|
BLAKE2b-256 checksum How to use checksums |
3628574ee4f6603d173752a2e15cecd7f24216d24aca1e82fa0c91b33d5d2bbb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 22, 2026.
Transparency logRelease files / grocker-8.3-py3-none-any.whl
| Download URL | grocker-8.3-py3-none-any.whl |
|---|---|
| Size | 24.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
16f4eebb2fb4ac78494cc1b5903830b3086842979ddfd3c4019afe238c03f2e4
|
|
BLAKE2b-256 checksum How to use checksums |
edefce47d82c0111586413963f2afa5993c6f60e2b913e43b4658d2869675a5e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 22, 2026.
Transparency log
