Here’s a common example of technical debt organizations frequently incur:
Business: is that new feature ready yet?
Developer: it seems to work but we haven’t finished the tests.
Business: if QA passes manual testing, ship it.
Developer: 😳
Business: add testing to the backlog.
Looking forward to the next relase of docker. You'll be able to pass in custom containerd shims like any other runtime.
`docker run --runtime=io.containerd.systemd.v1`
or
`docker run --runtime=io.containerd.wasmtime.v1`
or
`docker run --runtime=io.containerd.kata.v2`
If it doesn't solve the issue you are seeing, ping me on Rancher Users Slack and I can take a look at it: https://t.co/lRYayUTecc https://t.co/4oIXpzEbsW
@MyIgel@Rancher_Labs This should help figuring out why the default certificate is being served: https://t.co/4KiaMtcYGK
Regarding 503, it needs to communicate over the overlay network which needs UDP/8472 opened between nodes (https://t.co/TJTOqHybi4)