Ian Zhang

Results 10 comments of Ian Zhang

When using kubernetes and nydus，container failed to start with an error “target snapshot already exists”

> > Cloud you try `ctr images delete xxx/pause:3.6 --sync` ? > > Need to ensure the pod using the image has been deleted first. I have already deleted all...

Containerd fails to stop containers

encountering the same issue with containerd 1.6.23, any update here?

Loss can only be reduced to 130 ？！

so is that loss normal or not?

expected unqualified-id before numeric constant

same issue, do you have any solutions?

expected unqualified-id before numeric constant

> It seems to be a conflict with other constants. So I refactor these two variables to `ORACLE_OVERFLOW` and `ORACLE_UNDERFLOW`, then the compilation passed. thanks, i will try it

dataset/sol_map_contracts.jsonl not appeared in dataset.zip

have the same issue too. i would appreciate it if you can provide sol_map_contracts.jsonl! Thx a lot!

在centos8使用container 运行kata ,使用shared_fs = "virtio-fs"，会报Aug 24 11:13:15 localhost.localdomain kata[16081]: time="2023-08-24T11:13:15.262723838+08:00" level=error msg="qemu-system-x86_64: -chardev socket,id=char-e0b6621604f3272d,path=/run/vc/vm/kata-test/vhost-fs.sock: Failed to connect to '/run/vc/vm/kata-test/vhost-fs.sock': Connection refused" name=containerd-shim-v2 pid=16081 qemuPid=16092 sandbox=kata-test source=virtcontainers/hypervisor subsystem=qemu Aug 24 11:13:15 localhost.localdomain containerd[15767]: time="2023-08-24T11:13:15.262723838+08:00" level=error msg="qemu-system-x86_64: -chardev socket,id=char-e0b6621604f3272d,path=/run/vc/vm/kata-test/vhost-fs.sock: Failed to connect to '/run/vc/vm/kata-test/vhost-fs.sock': Connection refused" name=containerd-shim-v2 pid=16081 qemuPid=16092 sandbox=kata-test source=virtcontainers/hypervisor subsystem=qemu 这个错误用9p是正常的

this solved my issue, why use virtiofs not work??

在centos8使用container 运行kata ,使用shared_fs = "virtio-fs"，会报Aug 24 11:13:15 localhost.localdomain kata[16081]: time="2023-08-24T11:13:15.262723838+08:00" level=error msg="qemu-system-x86_64: -chardev socket,id=char-e0b6621604f3272d,path=/run/vc/vm/kata-test/vhost-fs.sock: Failed to connect to '/run/vc/vm/kata-test/vhost-fs.sock': Connection refused" name=containerd-shim-v2 pid=16081 qemuPid=16092 sandbox=kata-test source=virtcontainers/hypervisor subsystem=qemu Aug 24 11:13:15 localhost.localdomain containerd[15767]: time="2023-08-24T11:13:15.262723838+08:00" level=error msg="qemu-system-x86_64: -chardev socket,id=char-e0b6621604f3272d,path=/run/vc/vm/kata-test/vhost-fs.sock: Failed to connect to '/run/vc/vm/kata-test/vhost-fs.sock': Connection refused" name=containerd-shim-v2 pid=16081 qemuPid=16092 sandbox=kata-test source=virtcontainers/hypervisor subsystem=qemu 这个错误用9p是正常的

> @cl0udee ref: [#7107 (comment)](https://github.com/kata-containers/kata-containers/issues/7107#issuecomment-2128310586) that makes sense. my kernel version is below 5.10. thanks for helping!

Workload-updater ctrl: Cleanup with fakeclient, informers, patchset and libvmi

@HerlinCoder Excuse me for the interruption, but I noticed you have an PR related to supporting memory resizing with Dragonball. I guess you might have some valuable insights into my...

Workload-updater ctrl: Cleanup with fakeclient, informers, patchset and libvmi

@Apokleos Thanks for your response and these are additional explanations. It's worth noting that if you wish to patch a new container into a pod, you would need to modify...