Remove the embedded default user in alpine cloud

[afbjorklund]

There should not be a non-system user in the image.

Let cloud-init handle the users and groups instead.

Closes #2362

Fixes the boot on Linux, and then you can add nerdctl.

---

sudo apk add nerdctl containerd buildctl buildkit

lima-alpine-image:/home/anders$ sudo nerdctl version
Client:
 Version:	1.7.6
 OS/Arch:	linux/amd64
 Git commit:	<unknown>
 buildctl:
  Version:	0.12.5
  GitCommit:	alpine

Server:
 containerd:
  Version:	v1.7.10
  GitCommit:	4e1fe7492b9df85914c389d1f15a3ceedbb280ac
 runc:
  Version:	1.1.12
  GitCommit:	51d5e94601ceffbbd85688df1c928ecccbfa4685

lima-alpine-image:/home/anders$ df -h /dev/vda1 /dev/vda2
Filesystem      Size  Used Avail Use% Mounted on
/dev/vda1       486K  282K  204K  59% /boot/efi
/dev/vda2        94G  453M   90G   1% /

[AkihiroSuda]

Can we test this in CI?

[afbjorklund]

Can we test this in CI?

Testing on Linux should be enough, I think that Mac "got away" with it because it uses UID 500 ?

[jandubois]

I'm fine with deleting the alpine user; it only exists so you can test the image without setting up a cloud-init profile.

But I think we should make an exception if the local user is also called alpine. Otherwise we would have to use the lima user name inside the VM.

Note that I haven't tested if using alpine as a host username would work otherwise; maybe it would still be broken for other reasons.

[afbjorklund]

I'm fine with deleting the alpine user; it only exists so you can test the image without setting up a cloud-init profile.

I think that cloud-init should handle this anyway, by using the "default_user" and the distro default /etc/could config?

• User creation errors, with the new alpine-image template #2362 (comment)

So it should probably be made conditional, and not be called for "cloudinit" variant

[jandubois]

Thanks, LGTM