Closed matisiekpl closed 3 years ago
runsc is crashing because the RDTSCP
instruction is not supported.
What host CPU and kernel version are you using?
That instruction has been in x86 CPUs for 10+ years, so I imagine that the host does support it, but the hypervisor is disabling it in the guest.
Does Proxmox use QEMU+KVM? It seems there is some complexity about QEMU disabling RDTSCP on AMD guests because kernel support was added only a few years ago. It's not clear to me if they've merged patches to re-enable it, but it at least sounds possible to manually enabled with the appropriate flags.
@prattmic
I enabled the RDTSCP
flag on proxmox config, but I still getting following error:
root@vps10558:~# docker run -it --runtime=runsc ubuntu dmesg
docker: Error response from daemon: OCI runtime start failed: starting container: setting gofer oom_score_adj for container "3aee26e28473b2ce36699f953eeb2f99f8d1f042b76dfc175c59e5ed83b10047": write /proc/5180/oom_score_adj: invalid argument: unknown.
ERRO[0000] error waiting for container: context canceled
What should I do now? Thanks, Matt
Hm, that's a very different error. I assume this failure is consistent?
@ianlewis or @fvoznika will need to take a look.
Hm, that's a very different error. I assume this failure is consistent?
I don't know, I just want to use gVisor on my VPS. @prattmic Can it be caused by Proxmox vm setup? Or it's KVM-related bug?
@MatisiekPL It seems strange that it would be caused by the VM but I'm not really familiar with Proxmox.
A few questions come to mind:
Docker version: 19.03.6 I can run container using docker default runtime. And I have mounted /proc. How can I find runsc version?
For runsc version: runsc --version
Not sure why the call is failing with invalid argument
. Could you patch #1953 and run again to ensure the value being set is correct. Also, enable debug logging and attach the logs to here.
Since we don't validate oomScoreAdj from the OCI bundle it's possible that the value set there is either >1000 or <-1000 and thus causes this issue.
@MatisiekPL Can you try again with the latest version of runsc from HEAD so we can get more logging info?
This issue is stale because it has been open 90 days with no activity. Remove the stale label or comment or this will be closed in 30 days.
Hello. I want to run gvisor on Proxmox VM, but I can't it, because of following error
Proxmox vm options:
What should I do to run container in my vm?