Closed simonblake-mp closed 3 months ago
Thanks for the feedback about the Docker images. You're right that having versioned and up-to-date images would be better. I get that it's not ideal right now, but I won't be removing the existing images. With limited time, I've had to focus on other priorities first. But I understand versioned image releases are important. You can build the latest version from the source code for now (see the /docker folder).
Maybe this is something a public roadmap would help set expectations with? I'll work on it over the next couple of months, but contributions from you or others could help speed things up.
update: I've pushed new combined images for latest & 2.2.1 https://hub.docker.com/repository/docker/rwnxt/pynonymizer
This is going to be manual until we can get something in the build pipeline.
update:
I've added this job to the release pipeline. {{major}}.{{minor}} {{release}} and latest tags will be created automatically on new releases, so they should stay up to date!
I'm closing this issue now. Thanks for the feedback, and if there's anything else, let me know.
Describe the bug The docker images at https://hub.docker.com/r/rwnxt/pynonymizer/tags aren't version tagged, and haven't been updated in 18 days, so presumably aren't the most recent version of pynonymizer. While I totally get that they're experimental (and setting up a build pipeline is not super exciting), nothing is gained by having them sit rotting - probably they should be deleted if they're not going to be kept up to date.
Expected behavior Each pynonymizer release would cause a new set of containers to be released, tagged with the version, and "latest"
Additional context A link to the images in the README would be a good idea, if the intent is to keep them around as a first class artefact (which I hope you do, they're super useful) 🙏