batonogov/pyinstaller-linux and batonogov/pyinstaller-windows are Docker/Podman containers designed to simplify the process of compiling Python applications into binaries/executables.
Images available on multiple container registry:
-
batonogov/pyinstaller-windows/docker.io/batonogov/pyinstaller-windowsbatonogov/pyinstaller-linux/docker.io/batonogov/pyinstaller-linux
-
ghcr.io/batonogov/pyinstaller-windowsghcr.io/batonogov/pyinstaller-linux
For linux images have slim and bullseye/bookworm version will ensure better compatibility.
-slim-slim-bookworm-slim-bullseye
There are three containers, one for Linux and one for Windows builds.
The Windows builder runs Wine inside Ubuntu to emulate Windows in Docker.
To build your application, you need to mount your source code into the /src/ volume.
The source code directory should have your .spec file that PyInstaller generates. If you don't have one, you'll need to run PyInstaller once locally to generate it.
If the src folder has a requirements.txt file, the packages will be installed into the environment before PyInstaller runs.
For example, in the folder that has your source code, .spec file and requirements.txt:
docker run \
--volume "$(pwd):/src/" \
batonogov/pyinstaller-windows:latestwill build your PyInstaller project into dist/. The .exe file will have the same name as your .spec file.
docker run \
--volume "$(pwd):/src/" \
batonogov/pyinstaller-linux:latestwill build your PyInstaller project into dist/. The binary will have the same name as your .spec file.
You'll need to pass an environment variable called SPECFILE with the path (relative or absoulte) to your spec file, like so:
docker run \
--volume "$(pwd):/src/" \
--env SPECFILE=./main-nogui.spec \
batonogov/pyinstaller-linux:latestThis will build the executable from the spec file main-nogui.spec.
You'll need to supply a custom command to Docker to install system pacakges. Something like:
docker run \
--volume "$(pwd):/src/" \
--entrypoint /bin/sh batonogov/pyinstaller-linux:latest \
-c "apt update -y && apt install -y wget && /entrypoint.sh"Replace wget with the dependencies / package(s) you need to install.
docker run \
--volume "$(pwd):/src/" \
batonogov/pyinstaller-linux:latest \
"pyinstaller --onefile your-script.py"will generate a spec file for your-script.py in your current working directory. See the PyInstaller docs for more information.
Add pyinstaller==6.9.0 to your requirements.txt.
Yes, by supplying the PYPI_URL and PYPI_INDEX_URL environment variables that point to your PyPi mirror.
See example for GitLab CI.
windows_bin:
stage: deploy
image:
name: batonogov/pyinstaller-windows:latest
entrypoint: ['']
script:
- echo "Creating Windows artifact"
- pip install -r ./test/requirements.txt
- cd ./test && pyinstaller --onefile main.py
- cp ./dist/*.exe ../
rules:
- when: always
artifacts:
paths:
- '*.exe'
when: always
expire_in: 2 weekBitbucket doesn't support custom entrypoints, so we need to manually call it. Otherwise the setup is similar to what you would do with GitLab CI.
pipelines:
default:
- step:
name: Build Windows executable
image: batonogov/pyinstaller-windows:latest
artifacts:
paths:
- *.exe
script:
- echo "Creating Windows artifact"
- SPECFILE="$BITBUCKET_CLONE_DIR/sparvio-logger-bootstrap.spec" WORKDIR="$BITBUCKET_CLONE_DIR" bash /entrypoint.sh
- pip install -r ./test/requirements.txt
- cd ./test && pyinstaller --onefile main.py
- cp ./dist/*.exe ../Outdated Microsoft C++ Build Tools
Now release information will be here.
Release History
2023
- Linux container now uses Python base image
- Updated Pyintaller 5.8.0 -> 5.9.0
- Updated Python 3.11.2 -> 3.11.3
- Updated Python 3.11.1 -> 3.11.2
- Updated Ubuntu 20.04 -> 22.04 for windows
- Updated Pyintaller 5.7.0 -> 5.8.0
- New GitHub CI
- Added arm64 architecture in linux images
- Semver now
- Updated Pyintaller 5.5.0 -> 5.7.0
- Updated Python 3.10.8 -> 3.11.1
2022
- Python is compiled from sources
- Updated GitHub Actions (testing the image before push)
- Removed OpenSSL
- Updated Python 3.10.6 -> 3.10.8
- Updated Pyintaller 5.3.0 -> 5.5.0
- Optimized Dockerfiles
- Updated OpenSSL 1.1.1p -> 1.1.1q
- Updated Pyinstaler 5.2.0 -> 5.3.0
- Updated Python 3.10.5 -> 3.10.6
- Updated Python 3.10.4 -> 3.10.5
- Updated OpenSSL 1.1.1o -> 1.1.1p
- Updated Pyinstaler 5.1.0 -> 5.2.0
- Updated Pyinstaler 4.10 -> 5.1.0
- Updated OpenSSL 1.1.1n -> 1.1.1o
- Updated Ubuntu 20.04 -> 22.04 for amd64
- Updated Python 3.10.1 -> 3.10.4
- Updated Pyinstaler 4.7.0 -> 4.10
- Updated OpenSSL 1.1.1m -> 1.1.1n
2021
- Updated Python 3.10.0 -> 3.10.1
- Updated OpenSSL 1.1.1l -> 1.1.1m
- Updated Python 3.9.7 -> 3.10.0
- Updated Pyinstaler 4.5.1 -> 4.7.0
- Updated Ubuntu 12.04 -> 20.04 for amd64
- Updated openssl 1.0.2u -> 1.1.1l for amd64
- Deleted Python 2 Dockerfiles
- Deleted 32 bit Dockerfiles
- Updated Ubuntu 16.04 -> 20.04 for win64 and win32
- Updated PyInstaller 4.2 -> 4.5.1
- Updated Python 3.9.5 -> 3.9.7
- Drop support for Python 2.7
- Updated Python 3 to version 3.9
- Updated PyInstaller to version 4.2
2020
- Added a 32bit package, thank you @danielguardicore
- Updated PyInstaller to version 3.6
2019
- Build using an older version of glibc to improve compatibility, thank you @itouch5000
- Updated PyInstaller to version 3.4
2017
Added Python 3.6 on Windows, thanks to @jameshilliard
Changed the default PyInstaller version to 3.3
Fixed bug with concatenated commands in entrypoint arguments, thanks to @alph4
Upgraded PyInstaller to version 3.2.1. Thanks to @bmustiata for contributing:
- Custom PyPi URLs
- No longer need to supply a requirements.txt file if your project doesn't need it
- PyInstaller can be called directly, for e.g to generate a spec file
2016
Added Python 3.5 on Windows, thanks (again) to @bmustiata
Added Python 3.4 on Windows, thanks to @bmustiata
First release, works.
MIT