Docker images for CI Integration and building with PySide6, python3, and xvfb. https://hub.docker.com/r/ad5001/ubuntu-pyside-xvfb
Find a file
2024-09-24 17:35:51 +02:00
pyside2 Build system working with custom config files so I don't have to customize the script every time! 2024-09-20 01:05:08 +02:00
pyside6 Build system working with custom config files so I don't have to customize the script every time! 2024-09-20 01:05:08 +02:00
build.sh Fixing building process 2024-09-24 17:35:51 +02:00
LICENSE Reorganizing everything under a single repo 2024-09-19 19:03:32 +02:00
README.md Started automated building 2024-09-19 23:28:21 +02:00

docker-ubuntu-pyside-xvfb


This repository contains the Dockerfiles required to build all tags on Docker Hub:

All tags

  • a version of Python (v3.12 for PySide6, v3.10 for PySide2)
  • the tagged version of PySide2/6.
  • Python packages: pip, requests, packaging, pytest (+ pytest-cov + pytest-qt)
  • xvfb, xdotool, and wmctrl.

Linux tags

  • a Ubuntu base (noble for PySide6 and jammy for PySide2)
  • python3 is available under /usr/bin/python3.
  • External pip management disabled (allows you to install packages from pip directly).
  • make, git, rpm, and dh-python.

Additionally, the linux-6*-latex tag include a full TeXlive installation including dvipng and the latex extras.

Wine tags

  • The latest winehq-staging under a Ubuntu base.
  • /usr/bin/python calling python3 under wine.
  • /usr/bin/pip calling pip under wine.
  • /usr/bin/pyinstaller calling pyinstaller under wine.
  • wget, curl, git, p7zip-full, unzip and nsis.

Building docker files

It's recommended to use the build.sh bash script to build the Docker image. They use the config.toml in each directory to provide the data for each build, including the specific PySide versions to use for each.

Usage: bash build.sh [--pyside2] [--pyside6] [--latest] [--no-push] [--repo=ad5001/ubuntu-pyside-xvfb]

  • --pyside2: Build PySide2 images.
  • --pyside6: Build PySide6 images.
  • --latest: (Optional) Tag these as latest.
  • --no-push: (Optional) Do not push the tags to the Docker registry.
  • --repo: (Optional) Repository on the Docker registry which to push the images to.

NOTE: In Docker, use xvfb-run to run a program within a Xvfb server.