Kun
> 看了一部分源码，我猜测步骤如下 1. 将对docker-socket的请求 全部转发到lighthouse.sock上。 2. lighthouse会将请求转发给plugin-server 3. plugin-server prehook修改请求返回给lighthouse，目的可以看lighthouse的readme 4. lighthouse 将被修改的请求转发给docker 5. lighthouse 调用posthook
雀食，我的idea加载卡住了，好蛋疼，转战vs code
老哥如果修复了 记得戳我啊
I got the same problem, case when I try to use runc/libcontainer/cgroupmanager in container. Is there any chance to read file from environment, not just hard-coding "/run/systemd/system"
> > Also, a (somewhat nasty) workaround would be to do `mkdir /run/systemd/system`. Cause I run this in a container, I cannot use it unless I mount `/run/systemd` readonly on...
Set session into untrust solve this problem. It's better to add a cmd switch to control the request session whether use trust or verify 
#8 enhance for this issue
哥们怎么拉下来的，我一直报这个错 Error downloading object: investool/investool (c9382fb): Smudge error: Error downloading investool/investool (c9382fb2f081c6425e9c06023de683155f5376fae4e84f80a4737f40dd44dfb5): batch response: This repository is over its data quota. Account responsible for LFS bandwidth should purchase more data...