[GH-ISSUE #156] v1.0.4: tun/netstack does not compile with the pinned gVisor module #81

New issue

Open

opened 2026-10-13 21:03:23 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-13 21:03:23 +00:00

Owner

Originally created by @autopeasant on GitHub (Jul 23, 2026).
Original GitHub issue: https://github.com/amnezia-vpn/amneziawg-go/issues/156

Affected version

github.com/amnezia-vpn/amneziawg-go v1.0.4
Go 1.26.4
Linux amd64

Minimal reproduction

From an unmodified v1.0.4 module checkout:

go test ./tun/netstack

Observed behavior

The package cannot be compiled:

# github.com/amnezia-vpn/amneziawg-go/tun/netstack
.../gvisor.dev/gvisor@v0.0.0-20250606233247-e3c4c4cad86f/pkg/tcpip/adapters/gonet/gonet.go:29:2:
found packages stack (addressable_endpoint_state.go) and bridge (bridge_test.go) in .../pkg/tcpip/stack
FAIL github.com/amnezia-vpn/amneziawg-go/tun/netstack [setup failed]

Consequently, go test ./... also fails. After the setup failure is bypassed, the pinned gVisor module also lacks generated identifiers such as bits.MaskOf64, waiterEntry, and waiterList, which indicates that this gVisor revision does not provide a complete Go-module build for these packages.

Expected behavior

Every package exposed by the released Go module, including tun/netstack, should compile with go test ./... under a supported Go toolchain.

Pinning a gVisor revision whose published module contains the required generated sources (or build-tagging/removing tun/netstack when that dependency cannot be built with the Go toolchain) would restore the module-wide test/build invariant.

Originally created by @autopeasant on GitHub (Jul 23, 2026). Original GitHub issue: https://github.com/amnezia-vpn/amneziawg-go/issues/156 ## Affected version - `github.com/amnezia-vpn/amneziawg-go v1.0.4` - Go `1.26.4` - Linux amd64 ## Minimal reproduction From an unmodified v1.0.4 module checkout: ```sh go test ./tun/netstack ``` ## Observed behavior The package cannot be compiled: ```text # github.com/amnezia-vpn/amneziawg-go/tun/netstack .../gvisor.dev/gvisor@v0.0.0-20250606233247-e3c4c4cad86f/pkg/tcpip/adapters/gonet/gonet.go:29:2: found packages stack (addressable_endpoint_state.go) and bridge (bridge_test.go) in .../pkg/tcpip/stack FAIL github.com/amnezia-vpn/amneziawg-go/tun/netstack [setup failed] ``` Consequently, `go test ./...` also fails. After the setup failure is bypassed, the pinned gVisor module also lacks generated identifiers such as `bits.MaskOf64`, `waiterEntry`, and `waiterList`, which indicates that this gVisor revision does not provide a complete Go-module build for these packages. ## Expected behavior Every package exposed by the released Go module, including `tun/netstack`, should compile with `go test ./...` under a supported Go toolchain. Pinning a gVisor revision whose published module contains the required generated sources (or build-tagging/removing `tun/netstack` when that dependency cannot be built with the Go toolchain) would restore the module-wide test/build invariant.

bsakaguchi referenced this issue

2026-10-13 21:03:55 +00:00

[PR #81] [MERGED] Fix AWG build after merge #133