How solution work with containerd backend, without docker/podman client

[WAR-S]

Hi, i have arch linux, with k3s on board;
In k3s, I have crictl and containerd on the backend side, is it possible to run the agent in this configuration?

It would be cool if you had, for example, a prepared script;

Something like this (example):
crictl run -d
--name=$CONTAINER_NAME
--restart=on-failure
--privileged
--net=host
--pid=host
--mount type=bind,src=/,dst=/host,rw=true
--mount type=bind,src=/dev,dst=/dev,rw=true
--mount type=bind,src=/etc/passwd,dst=/etc/passwd,rw=true
--mount type=bind,src=/etc/group,dst=/etc/group,rw=true
--mount type=bind,src=/etc/resolv.conf,dst=/etc/resolv.conf,rw=true
--mount type=bind,src=/var/run,dst=/var/run,rw=true
--mount type=bind,src=/var/log,dst=/var/log,rw=true
--mount type=bind,src=/tmp,dst=/tmp,rw=true
--env SHELLHUB_SERVER_ADDRESS=$SERVER_ADDRESS
--env SHELLHUB_TENANT_ID=$TENANT_ID
$ARGS
shellhubio/agent:$AGENT_VERSION
$MODE

[gustavosbarreto]

I’m not really sure if that would work, as I don’t know k3s in enough details. I’d need to set up a k3s environment myself to properly test this scenario.

[otavio]

To better understand your setup and goal: are you trying to run the ShellHub agent on the host directly outside of Kubernetes, or are you aiming to run it inside Kubernetes, with one agent instance per host that has direct access to the host's resources (similar to how it would work with --privileged and host namespaces)?

[WAR-S]

Colleagues, thank you for your questions and answers, as far as I understand, i can simply compile the golang agent and put it in the systemd service.