Replies: 1 comment 3 replies
-
|
One option is to rework skipping bash. But your issue is that you copy Your container image should work on its own if you copy out the |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm trying to create extension for [netclient](https://github.com/gravitl/netclient). I have taken network/tailscale extension as template which resulted in following yamls:
Here is
pkg.yaml:netclient.yamlEverything seems to work: build, upgrade etc. except extension startup:
$ talosctl -n 192.168.0.187 upgrade --image docker.io/ljachym/talos-metal-installer:v1.9.2@sha256:83894a4c9375a465e1780d9482d528f3e4df22654f68e65ba71424a838dc75e9 WARNING: 192.168.0.187: server version 1.9.2 is older than client version 1.9.3 watching nodes: [192.168.0.187] * 192.168.0.187: post check passed isolated@13cf64a34911:~$ talosctl -n 192.168.0.187 service NODE SERVICE STATE HEALTH LAST CHANGE LAST EVENT 192.168.0.187 apid Running OK 17s ago Health check successful 192.168.0.187 auditd Running OK 32s ago Health check successful 192.168.0.187 containerd Running OK 32s ago Health check successful 192.168.0.187 cri Running OK 23s ago Health check successful 192.168.0.187 dashboard Running ? 25s ago Process Process(["/sbin/dashboard"]) started with PID 1998 192.168.0.187 ext-netmaker-client Waiting ? 1s ago Error running Containerd(ext-netmaker-client), going to restart forever: task "ext-netmaker-client" failed: exit code 255 192.168.0.187 kubelet Running OK 20s ago Health check successful 192.168.0.187 machined Running OK 32s ago Health check successful 192.168.0.187 syslogd Running OK 31s ago Health check successful 192.168.0.187 udevd Running OK 26s ago Health check successful isolated@13cf64a34911:~$ talosctl -n 192.168.0.187 logs ext-netmaker-client 192.168.0.187: exec /usr/local/bin/bash: no such file or directory 192.168.0.187: exec /usr/local/bin/bash: no such file or directory 192.168.0.187: exec /usr/local/bin/bash: no such file or directory 192.168.0.187: exec /usr/local/bin/bash: no such file or directory 192.168.0.187: exec /usr/local/bin/bash: no such file or directory 192.168.0.187: exec /usr/local/bin/bash: no such file or directorySo it seems that /usr/local/bin/bash is not available inside extension container although I'm copying it during install phase of pkg.yaml. Can anybody point me to solution here? How to use bash inside of extension container properly? Tailscale does not have this issue because they have [containerboot command - tailscale.com/cmd/containerboot - Go Packages](https://pkg.go.dev/tailscale.com@v1.40.1/cmd/containerboot) which unfortunately is not the case for netclient, see their dockerfile: [netclient/Dockerfile at develop · gravitl/netclient](https://github.com/gravitl/netclient/blob/develop/Dockerfile) and bash wrapper used to launch it: https://github.com/gravitl/netclient/blob/develop/scripts/netclient.sh
Here is code for adding netclient extension: https://github.com/b1r3k/extensions/tree/adds-netmaker-netclient
Beta Was this translation helpful? Give feedback.
All reactions