Re: Need help with lazy module loading & gvisor
On Sat, Sep 10, 2022 at 4:38 AM John Goerzen <jgoerzen@complete.org> wrote:
>
> On Fri, Sep 09 2022, Shengjing Zhu wrote:
>
> > Hi,
> >
> > On Sat, Sep 10, 2022 at 3:59 AM John Goerzen <jgoerzen@complete.org> wrote:
> >> (you can see I tried everything I could think of to stop the tools stuff
> >> from being installed)
> >>
> >> I've pushed the tree I have so far to
> >> https://salsa.debian.org/go-team/packages/golang-gvisor-gvisor so you
> >> can take a look if you like.
> >>
> >
> > I haven't looked in depth, but I have looked gvsior before, I believe
> > you have used a wrong upstream branch.
> > You should use https://github.com/google/gvisor/tree/go
>
> That is what is being used here:
>
> [remote "gvisor"]
> url = https://github.com/google/gvisor
> fetch = +refs/heads/*:refs/remotes/gvisor/*
>
> In any case, I would likely still be stuck at how to exclude tools.
>
I mean, you need to use the `go` branch, instead of the `master` branch.
In the `go` branch, there is only one subdir in the `tools` dir, which
is easy to exclude.
> > BTW, I have thought of packaging runsc(the binary from gvisor) before,
> > which is a nice container runtime.
>
> Maybe once we get this in unstable as a library to solve the immediate
> problem, it could be expanded, indeed.
>
> - John
>
--
Shengjing Zhu
Reply to: