Skip to content

Conversation

@fahedouch
Copy link
Contributor

No description provided.

@fahedouch fahedouch force-pushed the build-tags-omit-network-drivers branch 2 times, most recently from b123542 to 95cf9e5 Compare October 8, 2025 14:23
The child command can enter `$ROOTLESSKIT_STATE_DIR/netns` by itself to create nested network namespaces.


## Build tags to omit drivers
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be probably in /BUILDING.md

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

docs/network.md Outdated
go build -tags no_slirp4netns ./cmd/rootlesskit

- Build without lxc-user-nic support:
go build -tags no_lxcusernic ./cmd/rootlesskit
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only one example should suffice for a document.

The CI should test all of them, and a combination of them too.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed, but I what to test here ?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just test go build with several combination s of the tags

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added some tests


// NewParentDriver returns a stub when built with the no_gvisortapvsock tag.
func NewParentDriver(logWriter io.Writer, mtu int, ipnet *net.IPNet, ifname string, disableHostLoopback bool, enableIPv6 bool) (network.ParentDriver, error) {
return &disabledParent{}, errors.New("gvisor-tap-vsock network driver disabled by build tag no_gvisortapvsock")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Omitted drivers should not appear in --help

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

@fahedouch fahedouch force-pushed the build-tags-omit-network-drivers branch from 4c89ecd to e13e7de Compare October 21, 2025 08:56
@fahedouch fahedouch requested a review from AkihiroSuda October 21, 2025 08:56
@fahedouch fahedouch force-pushed the build-tags-omit-network-drivers branch from 4e968b8 to a91432a Compare October 24, 2025 16:24
@fahedouch
Copy link
Contributor Author

@AkihiroSuda PTAL

@AkihiroSuda AkihiroSuda added this to the v3.0.0 milestone Oct 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants