upgrade base image to debian 12 and tor daemon to 0.4.8.13#31
Conversation
|
Good to see someone also working on this important repository. |
|
Hi @lnliz ! I went with maintaining the fork and have added some features like a default torrc file that binds to all ports and serves the SOCKS proxy for easy integration into other projects. Also cleaned up a lot of workflows and reworked the readme. I no longer expect this to be merged and will keep the fork up to date more like an alternative image. The images are now built and published in GitHub. Thanks for your work as well! |
|
Thank you for your public contributions @m0wer - this is very good and I learned a lot and will use some for my fork too |
- actions/checkout: v5 → v6.0.2 - docker/login-action: v3 → v4.2.0 - docker/metadata-action: v5 → v6.1.0 - docker/build-push-action: v5 → v7.2.0 - Add docker/setup-qemu-action@v4.1.0 - Add docker/setup-buildx-action@v4.1.0 - Build for: linux/amd64, linux/arm64, linux/arm/v7, linux/arm/v6, linux/386, linux/ppc64le, linux/s390x
- Build each platform in a matrix job for parallel execution - Use ubuntu-24.04-arm for native linux/arm64 builds - Keep QEMU only for non-native architectures - Add per-arch GHA build cache scopes - Merge per-arch images into final multi-arch manifests
Add post-merge manifest verification for all published tags to ensure linux/amd64, linux/arm64, linux/arm/v7, linux/arm/v6, linux/386, linux/ppc64le, and linux/s390x are all present.
2 participants
Based on #30 but a bit more up to date. Fixes #13 and #21.
I will mantain the fork in my repo until merged. I've enabled CI to automatically build and publish the images to ghcr.io/m0wer/docker-tor
The ci commit should be removed before merging unless you also want to publish images to the GitHub image registry.