Max Satula

Here are my findings: Microk8s's snap squashfs image contains coreutils version 8.28, which provides `uname` and `cp` utilities `cp -r /snap/microk8s/2347/default-args /var/snap/microk8s/2347/args` command is expected to create `args` directory in...

Also had to replace `/bin/sleep` with the one on the host, as it segfaulted too... Now I've seen the services running for a while, then it failed with > Start...

Even after replacing more failing binaries/libs and finally installing microk8s a simple `microk8s status` segfaults on calling python3. I'm giving up. That seems to be a general snap problem, not...

> You can change this by editing the boot config to use kernel 4.18 Thanks for that, better than nothing, however that is more of a workaround rather than a...

@tgie that seems to fix for x86_64, aarch64 still has a problem

> By setting option `follow: true`, `await contatiner.logs()` returns a stream, with `follow: false` it returns a string. Sometimes with `follow: false` an output log is still enormous; I would...

Still having an issue, although it is arm64 not x86_64 ``` # uname -a Linux oci-arm-dev 5.4.17-2136.307.3.5.el8uek.aarch64 #2 SMP Thu May 26 18:21:01 PDT 2022 aarch64 aarch64 aarch64 GNU/Linux #...

> @maxsatula this looks to be a different issue than reported by @LenzGr. His error message was `cannot execute binary file`. Do you have reason to believe it's the same...

@a17r you did not have to drop dev-db/ocp-0.2-r1, but that's ok with me. ACK for dev-db/ocp

Tried both 4.1.0 and 4.2.0 versions