Colima fails during initialization process due to missing iptables dependencies

[tiilikainen]

Description

Encountered this during reboot after upgrading from 0.6.2 to 0.6.5, running colima delete, and then running the fix to install sshfs after I encountered that error.

INFO[0013] starting colima
INFO[0013] runtime: docker
INFO[0013] creating and starting ...                     context=vm
>   Package libnftnl11 is not installed.
>
> dpkg: error processing package iptables (--install):
>  dependency problems - leaving unconfigured
> Errors were encountered while processing:
>  iptables
> The following packages have unmet dependencies:
>  iptables : Depends: libip6tc2 (= 1.8.9-2ubuntu2) but it is not going to be installed
>             Depends: libnetfilter-conntrack3 (>= 1.0.6) but it is not going to be installed
>             Depends: libnfnetlink0 (>= 1.0.2) but it is not going to be installed
>             Depends: libnftnl11 (>= 1.1.6) but it is not going to be installed
> E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).
FATA[0390] error starting vm: error at 'creating and starting': error at 'starting': error installing packages using mantic-debs: exit status 100

Thankfully, the suggested workaround apt --fix-broken install actually worked, as I was able to get colima to build and start a container, but I thought I would report this nonetheless.

Version

colima version 0.6.5
git commit: a3adebfcd9da8c85614d81030033d02f04908a79

runtime: docker
arch: x86_64
client: v24.0.7
server: v24.0.7
limactl version 0.18.0
qemu-img version 8.1.2

Operating System

• macOS Intel <= 13 (Ventura)
• macOS Intel >= 14 (Sonoma)
• Apple Silicon <= 13 (Ventura)
• Apple Silicon >= 14 (Sonoma)
• Linux

Output of colima status

INFO[0000] colima is running using QEMU
INFO[0000] arch: x86_64
INFO[0000] runtime: docker
INFO[0000] mountType: sshfs
INFO[0000] socket: unix:///Users/<my user ID>/.colima/default/docker.sock

Reproduction Steps

1. brew upgrade colima (currently updates to Colima 0.6.5)
2. colima delete
3. colima start --edit (change: CPUs from 2 -> 4, memory from 2 -> 8, and add a docker registry)
   (here Colima gets stuck waiting for sshfs to get installed)
4. colima ssh -- sh -c "sudo apt-get update && sudo apt-get install -y -o Dpkg::Options::=--force-confdef -o Dpkg::Options::=--force-confnew sshfs"
   (Colima passes that step, reboots, and then gets stuck on the message posted in the description above)

Expected behaviour

The expected behavior is that after reproduction step 4 above, Colima starts normally. (Ideally, step 4 wouldn't be needed at all either.)

Additional context

No response

[rfay]

I think this is a duplicate of

• Colima 0.6.4+: Start fails with "dependency problems - leaving unconfigured" (workaround colima prune) #888

But it does seem to be resolved with colima prune

[abiosoft]

This should be fixed in v0.6.7.