Hey, this is a known regression in the CLI version 2026.04.13-a9d7fb5. There have been a few reports of the same issue in the last 24 hours:
The team is aware of it. While they’re investigating, you can try rolling back to the previous CLI version 2026.03.20-7da3412. Another user confirmed it worked fine there.
About the SELinux alerts with bwrap, that’s most likely a side effect of sandboxing in the container, not the root cause. The CPU spike also reproduces outside containers.
Let me know if the rollback helps.