![]() ![]() # ctr run -runtime io.2 -t -rm docker.io/library/busybox:latest cshĬtr: Failed to check if grpc server is working: rpc error: code = DeadlineExceeded desc = timed out connecting to vsock 823476853:1024: unknownĭEBU stat snapshot key="sha256:de168d3b8ec4765250376be559836953e27ff721fff3bc1124dd758bb153ce51"ĭEBU prepare snapshot key=csh parent="sha256:de168d3b8ec4765250376be559836953e27ff721fff3bc1124dd758bb153ce51"ĭEBU event published ns=default topic=/snapshot/prepare type=ĭEBU get snapshot mounts key=cshĭEBU event published ns=default topic=/containers/create type= (4) See RPC Error: ctr: Failed to check if grpc server is working: rpc error: code = DeadlineExceeded desc = timed out connecting to vsock 823476853:1024: unknown (2) Using kata-runtime 2.0.0 (with AMD SEV mem_encryption changes):Ĭommit : fed5a81d373c5cb4d4a3961b5731407729572ea2-dirtyĬonfigPath = "/etc/kata-containers/configuration.toml"īinaryName = "/usr/local/bin/kata-runtime" ![]() ![]() (1) Using containerd version 1.3.3 on Ubuntu "20.04.1 LTS (Focal Fossa)" Host:Ĭontainerd /containerd/containerd 1.3.3-0ubuntu2.2 Subject: Regarding, RPC Error with kata-runtime, kata 2.x (kata-containers-stable-2.0.0) with mem_encryption (AMD SEV) enabledĪny suggestions for the following please. Not sure if this email made it to the kata-dev list, If not could you please forward to the kata-dev list ?Ĭc: Gupta, Sandeep Hollingsworth, Brent Subject: FW: Regarding, RPC Error with kata-runtime, kata 2.x (kata-containers-stable-2.0.0) with mem_encryption (AMD SEV) enabled Next message (by thread): Shimv2 and CRI-O clarifications.Previous message (by thread): Regarding, RPC Error with kata-runtime, kata 2.x (kata-containers-stable-2.0.0) with mem_encryption (AMD SEV) enabled.FW: Regarding, RPC Error with kata-runtime, kata 2.x (kata-containers-stable-2.0.0) with mem_encryption (AMD SEV) enabled Venegas Munoz, Jose Carlos at ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |