cross-posted from: https://lemmy.ml/post/26615546
The official docker image is still at v0.11 and was last updated in 2016. It looks like maybe
trunkis at 0.12, but, as far as I can tell, that a rolling release. My prosody install is too important to go with a rolling release.Both the alternatives that they point to are similarly old;
- v0.11.13 --- https://github.com/OpusVL/prosody-docker/
- v0.11.x (?) --- https://github.com/unclev/prosody-docker-extended
My server is langishing on the unclev image. I'd like to migrate to something with 0.12 and have a bit more confidence in its resiliance.
5 Comments
vk6flab@lemmy.radio · 4 pts · 1y
I rarely use a docker container in production that I didn't write the Dockerfile for. Once you understand how it works, you can write your own and install exactly what you want in the way you want it.
truthfultemporarily@feddit.org · 9 pts · 1y
Exactly the opposite for me, using official container images is a major time save.
sugar_in_your_tea@sh.itjust.works · 4 pts · 1y
Yeah, they're much better at updating them than I am.
qwexfle@lemmy.ml · 1 pts · 1y
That would probably the best practice. But as another post said, I don't trust myself (and I lack the skills, although that's pretty lame excuse).
Yaky@slrpnk.net · 1 pts · 1y
When I ran prosody a few years ago, I did so without docker.
I did try snikket in docker though, and it looks like it is still actively maintained.