-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rebuild #1
Comments
What if you |
I have the latest build, https://hub.docker.com/r/indiehosters/known/builds/bkk8nxlszwyg6fck9xddxl3/. The image ID at the bottom of the build log matches the one being used for my domain:
https://edrex.pdxhub.org/admin/about still reports 0.9.2 after |
Ah, issue is that the base known image is still at 0.9.2. I'll go upstream. Maybe keep this as a tracking issue? |
For now I've forked this repo and the upstream one and set up an autobuilder at https://hub.docker.com/r/pdxhub/known-withplugins/ |
idno/Known-Docker#2 (comment) is now closed. Does this affect the build from here; are we up to date, yet? |
Not sure. Anyway the latest release is almost 2 years old and over 2000 commits behind master, which is I think what they're running their hosted service from. |
Thanks for following up here. Can we put our strings a little together, and build from master instead? Could be good to know if there's an up to date Dockerfile somewhere, and if the plugins still match up to all those changes introduced. |
Revisiting this here although it should be moved to https://lab.libreho.st/libre.sh/docker/known/issues https://github.com/idno/known/releases/tag/1.0.0 Official docker image isn't updated but https://hub.docker.com/r/egoexpress/known is. |
First pass: idno/Known-Docker#12 |
current docker image self-reports as 0.9.2, while 0.9.9 is available. Looks like the Dockerfile is pulling master, so a forced rebuild should be sufficient. @pierreozoux ?
The text was updated successfully, but these errors were encountered: