Skip to content
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

Bug Report/Feature-ish request: debian package should provide container runtime version constraint #355

Closed
3 tasks done
donaldguy opened this issue Jan 28, 2024 · 2 comments
Labels
bug Something isn't working stale

Comments

@donaldguy
Copy link

OS Version

Debian GNU/Linux 12 (bookworm)

System Information

Linux odroidn2 6.1.63-current-meson64 #1 SMP PREEMPT Mon Nov 20 10:52:19 UTC 2023 aarch64 GNU/Linux

What happened?

I have been expressing this opinion over in home-assistant/supervisor#4834 and I decided to get off my butt and put the point over here where it rather belongs.

In light of what has happened with home-assistant/supervisor#4827 (Docker 25.0.0 breaking hassio network initialization), I think its clear that this package should be providing either some pin/constraint or an out-right hold on the docker-ce packages to a known good version.

self-quoting from home-assistant/supervisor#4834 (comment) :

...
and/but then speaking as a supervised-installer user, I would say (again, as in PR descrip) that this pin/constraint should absolutely be in the debian package metadata (https://github.com/home-assistant/supervised-installer/blob/main/homeassistant-supervised/DEBIAN/control) or at least the https://github.com/home-assistant/supervised-installer/blob/main/homeassistant-supervised/DEBIAN/postinst should call the relevant apt-mark holds

I am willing to have HASSIO holding-back this machine from taking on newer docker engine, but I am pretty peeved to have it break on apt upgrade


That said, my suspicion is that HA et al are facing down a bigger container runtime reckoning sooner-rather-than later, with cgroups v1 officially officially deprecated (for sometime-this-year removal) in systemd 255

and with that a question of e.g. jumping ship(/"jumping whale") from docker/moby entirely to podman, or systemd-nspawn, or whatever.

It did not escape my notice that the /usr/sbin/hassio-supervisor run command recently grew a containerd.sock mount

So ... there's that.

(Also if this is getting any eyes, I would also like to highlight my concerning apparmor related findings over in home-assistant/supervisor#4839 - something that amongst other implications, suggests there may be pins for other packages in Debian 12 in urgent-ish order)

Machine Type

odroid-n2

Installer output

No response

Relevant log output

No response

ADR

  • I have read through the ADR and have confirmed that my system is compliant with the requirements
  • I understand that if my system is found to not be compliant, my issue will be closed immediately without further investigation

Code of Conduct

@donaldguy donaldguy added the bug Something isn't working label Jan 28, 2024
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label May 28, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working stale
Projects
None yet
Development

No branches or pull requests

2 participants