Proposed Improvements for the Scribus Docker Image

[ricardobalk]

Upon reviewing the Scribus Docker image, which hasn't been updated for two years, I have identified several areas that need enhancement to ensure increased efficiency and usability:

• Registry Shift: To facilitate a more streamlined approach, I am planning to shift to the ghcr.io registry.
• Version Pinning: The Docker image currently lacks a specified Scribus version. To rectify this, I intend to pin the version of Scribus used within the image, allowing me to tag images accurately in the ricardobalk/scribus-headless:x.y.z format. This would strengthen version control and simplify the rollback process.
• Multi-stage Builds: The Docker image currently comprises an entire Ubuntu Focal system, which is not strictly necessary for Scribus operation. By introducing multi-stage builds, the image size could be significantly reduced while maintaining operational efficiency.
• Automated Builds: At present, builds are manually generated, which can be a lengthy and error-prone process. Given Docker Hub's recent build restrictions, I propose to automate this process using ghcr.io in tandem with GitHub Actions to improve reliability.
• Multi-arch Builds: To broaden the compatibility of the Docker image, it would be beneficial to include multi-architecture support. With the advent of the Apple M1 chip (arm64), supporting both ARM64 and AMD64 architectures will be considered.