I think —DOCKER— is doing this. I installed based, and userspace(7)-pilled liblxc and libvirt and then this asshole inserted a dependency when I tried to install from their Debian package with sudo dpkg -i. One of them was qemu-system, the other was docker-cli because they were forcing me to use Docker-Desktop, which I would not be caught dead using.

So is this accidental, or another predatory move by one of these ‘ooh I wish I did not open source’ companies (e.g. HashiCorp)? Why don’t we all use LXC and ditch this piece of shit?

I could be misunderstanding how Debian-based packaging works. But this is too ‘’‘accidental’‘’. Correct me if I am wrong.

uname -a for context:

Linux pop-os 6.8.0-76060800daily20240311-generic #202403110203~1714077665~22.04~4c8e9a0 SMP PREEMPT_DYNAMIC Thu A x86_64 x86_64 x86_64 GNU/Linux
  • SteveTech@programming.devEnglish
    6·
    6 months ago

    How can I do that with dpkg(1)?

    You can install .deb files with apt by prepending a ./, e.g. sudo apt install --no-install-recommends ./docker-desktop-4.30.0-amd64.deb would work. I usually avoid using dpkg unless I have to.

    Also:

    • That deb file is for docker desktop, which you said you didn’t want?
    • Is insapp an alias or something?
    • You were running sudo apt-get install -f before, was your install already broken?