Chen Chen
Chen Chen
Please tell me the porting labels to be applied.
@maxwolffe please set overlaybd-apply log level to 'debug' to get more info. https://github.com/data-accelerator/overlaybd-apply/blob/main/src/tools/overlaybd-apply.cpp#L64 ``` set_log_output_level(0); ```
@maxwolffe sorry, the setting is overwrite by the following config in 'imgservice'. So please set the log level in config file instead. The config is stored in '/etc/overlaybd/overlaybd.json' by default....
@maxwolffe the "no space left" means our lsmt block device whose default size is 64 GB per layer. However it also maybe bugs in extfs. About the testing image: 1....
@bergwolf Thanks for commenting! Kata Containers has already supported using block device as container's rootfs, and it is the only way for firecracker. Device mapper is the only supported block...
What does "add-pr-size-label" failed mean ?
> @yuchen0cc Could you please merge `kata-containers:main` into your branch, I think one of the PR checks is failing because the branch is not up to date? OK, I've rebase...
@sazzy4o sorry to forget this checking, I've fixed it.
As suggested by @bergwolf , I think there is no longer need to check multiple templates (using map and loop). So I squash the previous 2 commit and make it...
TestIsDeviceMapper has been moved from [mount_test.go](https://github.com/kata-containers/kata-containers/blob/main/src/runtime/virtcontainers/mount_test.go) to [mount_linux_test](https://github.com/kata-containers/kata-containers/blob/main/src/runtime/virtcontainers/mount_linux_test.go) I need to move correspondingly.