This message was deleted.

does not include, it is pure upstream k3s - currently trying to make it run

hmm, I see. I would have assumed it did (https://github.com/k3s-io/k3s/issues/2918)

aha, maybe it is 🙂

I feel it is included there somewhere, but no idea how to enable :S (

ctr plugins ls

doesn’t show it)

could you please try this? ~/Library/Application\ Support/rancher-desktop/lima/_config/override.yaml

env:
  ADDITIONAL_ARGS: --snapshotter=stargz

Does that work if I have kubernetes disabled?

I don't think so, as it is argument for k3s/kubernetes

I ended up compiling it inside the VM as the default release from github didn’t seem to work out of the box ^^; Then set up in same way via OpenRC as containerd. tbh, I would prefer to switch to Ubuntu-based image with everything configured via systemd.

Hi, I ended up with this

override.yaml

and it is persistent, but the config is probably not correct/complete, anyway it might be usefull for you.

containerd:
  system: true # official provisioning system script will be triggered just once on initial run so cusom config.toml will be used
provision:
  - mode: system
	script: |
	  #!/bin/sh
	  apk update
	  apk add mkcert --force-broken-world --repository <https://dl-cdn.alpinelinux.org/alpine/edge/testing>
	  apk add libc6-compat
	  wget <https://github.com/containerd/stargz-snapshotter/releases/download/v0.12.0/stargz-snapshotter-v0.12.0-linux-amd64.tar.gz>
	  tar xf stargz-snapshotter-v0.12.0-linux-amd64.tar.gz
	  ./containerd-stargz-grpc &
  - mode: system
	script: |
	  #!/bin/sh
	  cat <<'EOF' >> /etc/containerd/config.toml
	  version = 2

	  # Plug stargz snapshotter into containerd
	  # Containerd recognizes stargz snapshotter through specified socket address.
	  # The specified address below is the default which stargz snapshotter listen to.
	  [proxy_plugins]
		[proxy_plugins.stargz]
		  type = "snapshot"
		  address = "/run/containerd-stargz-grpc/containerd-stargz-grpc.sock"

	  # Use stargz snapshotter through CRI
	  [plugins."io.containerd.grpc.v1.cri".containerd]
		snapshotter = "stargz"
		disable_snapshot_annotations = false
	  EOF

hmm, I see. I’ll try that one

but the config is wrong and RD report an error

containerd:
  system

seems to require systemd. It seems there are quite many things that need changing in order to get this to work. I’ll take a look later if I can get this approach work by using Ubuntu image containing systemd (alpine doesn’t seem to support systemd out of the box..?).

alpine is using openRC instead of systemd

yes, so the above approach doesn’t work with the default image

why? there is nothing systemd specific

I tried switching to Ubuntu 22.04 image but getting error:

/Applications/Rancher <http://Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl|Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl> shell --workdir=. 0 sudo /sbin/rc-service --ifstarted k3s stop

Apparently RD tries to install k3s using openrc even though the OS is systemd-based

containerd.system

is about running provisioning scripts for containerd - it has nothing to do with systemd

btw, is it possible to pass to RD/k3s some parameters to make it use systemd?

k3s itself supports systemd but alpine limavm doesn't - you'd need to rewrite lot of stuff (image, provisioning scripts, etc...)

hmm, i see. I’ll try with openrc again. maybe had wrong conf somewhere.

no idea

@freezing-airplane-30363 It doesn’t seem to work.

containerd.system: true

seems to require systemd:

`time="2022-08-10T12:46:07+09:00" level=fatal msg="degraded, status={Running:true Degraded:true Exiting:false Errors:[1 error occurred:\\n\\t* failed to satisfy the optional requirement 1 of 2 \\"systemd must be available\\": systemd is required to run containerd, but does not seem to be available.\\nMake sure that you use an image that supports systemd. If you do not want to run\\ncontainerd, please make sure that both 'container.system' and 'containerd.user'\\nare set to 'false' in the config file.\\n; skipping further checks: stdout=\\"\\", stderr=\\"+ command -v systemctl\\\\n+ echo 'systemd is not available on this OS'\\\\nsystemd is not available on this OS\\\\n+ exit 1\\\\n\\": failed to execute script \\"systemd must be available\\": stdout=\\"\\", stderr=\\"+ command -v systemctl\\\\n+ echo 'systemd is not available on this OS'\\\\nsystemd is not available on this OS\\\\n+ exit 1\\\\n\\": exit status 1\\n\\n] SSHLocalPort:59256}"\n`,
  code: 1,
  command: [
    '/Applications/Rancher <http://Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl|Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl>',
    'start',
    '--tty=false',
    '/Users/.../Library/Application Support/rancher-desktop/lima/_config/0.yaml'
  ]
}

Hm, seems you are right