5 ms·
> We have developed libcontainer in the hope that other projects will reuse it. Any plans on making that into a separate repo? I thought that would be more com
by songgao 13y ago
> We have developed libcontainer in the hope that other projects will reuse it.
Any plans on making that into a separate repo? I thought that would be more community friendly and easier to envolve.
In addition, dokcer/pkg/netlink [0] seems to be a package that others can use as well. Also, any plans on adding IPv6 support to that [1] or is pull requests for that welcomed?
[0] https://github.com/dotcloud/docker/tree/master/pkg/netlink https://github.com/dotcloud/docker/tree/master/pkg/netlink
[1] https://github.com/dotcloud/docker/blob/master/pkg/netlink/netlink_linux.go#L711 https://github.com/dotcloud/docker/blob/master/pkg/netlink/n...
- jamtur01 13y agoCurrently we don't have any plans to make it a separate repository. This is largely because of packaging issues - most of the distros currently struggle with packaging Go components. We're working closely with them to make this better but in the meantime libcontainer lives in the pkg/ directory to make it easier for us to ship Docker. You can most certainly use netlink in the same way and we'd love a PR for IPv6 support for it!
- voidlogic 13y agoCan you explain this? How is it hard to package a statically linked binary into an rpm or deb? How can it be harder than a C program? Are you talking about creating -dev packages?
- crosbymichael 13y agoYou can still use these packages with the slightly longer import path util we find a solution that works for everyone. import "github.com/dotcloud/docker/pkg/libcontainer" import "github.com/dotcloud/docker/pkg/netlink"