-
Notifications
You must be signed in to change notification settings - Fork 7
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
Merge all into main #298
Merge all into main #298
Conversation
Bumps debian from bookworm-20240513-slim to bookworm-20240612-slim. --- updated-dependencies: - dependency-name: debian dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]>
…m-20240612-slim' into merge-all-into-main
* add build cleaning script * apt: use autoremove that doesn't sometimes miss stuff
* Update Dockerfile.mlatclient Updated instructions on how to use this baseimage * Update Dockerfile.mlatclient --------- Co-authored-by: Fred Clausen <[email protected]>
@wiedehopf tagging you for visibility in case you have any comments. |
So just as a comment, it would seem that the PR workflow triggred a rebuild of https://github.com/sdr-enthusiasts/docker-reversewebproxy/actions ? That doesn't seem quite right. Oh not of only reverseproxy but also a bunch of other containers. |
That's actually intentional. I made that change when we updated to bookworm. It rebuilds them so we can test containers built against the new test base images, but it isn't pushing either the new base images or the other containers to latest. It uses |
This includes all of the open/recent PRs that we were holding off on. I think.
baseimage-test
on all of the SDR-E stack containers. They'll auto build with this PR.I'll test once the stack is built, but it would be nice to have someone else test too :)