Philipp Buehler

Built a docker image as per the example @rgl mentioned here already to no avail: The "touch" is going nowhere and thus the rebootWatch() never fires. A manual touch in...

Same issue here; running on macOS with vagrant-virtualbox. I tracked this down in the tink-docker container where you can find this: ```` {"level":"info","ts":1651047221.0680003,"caller":"cmd/root.go:45" *msg": "starting","service":"github.com/tinkerbell/tink","version": "2h87714"} Error: worker Finished with...

ok, this is gRPC and has nothing along docker certs. the `ca.pem` needs to be added to the tink-worker container FS (/etc/ssl/certs/ca-certificates.crt or extra /etc/ssl/certs/myveryca.pem -- both work). Fiddling on...

fallout from https://github.com/tinkerbell/tink/pull/584

Caused.. I was able to rollback the image hashes used in the sandbox and there it works. More bits of diagnose and blister help in this issue https://github.com/tinkerbell/sandbox/issues/133

@varilci at that kvm console, can you check the tink-worker logs please: ```` (press enter, there IS a prompt "hidden" with the kernel message along IPVS) # ctr -n services.linuxkit...

yeah, that's the one. What I found so far, that this is likely related to https://github.com/tinkerbell/tink/pull/584 basically the whole thing wont work with "unofficial"/selfsigned certs any longer. In `sandbox` I...

Ok, the "full" change to make my sandbox-vagrant-vbox setup going is with these hashes and a change on the Boots cmdline, since they changed somewhen around that. Might be more...

There's a second reason this can hang (just when hook tries to download tink-worker) and that's along "ca.pem". Remove that after failed tries before starting the next up/provision of the...

Hmm, can't tell why/where the 2nd attempt hangs at. Check logs of tink-docker again. ca.pem is in `deploy/compose/state/webroot/workflow` after the initial provisioning - only delete it for a fresh start,...