Skip to content

chore(deps): bump Go dependencies - #197

Merged
FloSch62 merged 4 commits into
mainfrom
chore/bump-deps
Nov 7, 2026
Merged

FloSch62 merged 4 commits into
mainfrom
chore/bump-deps

Conversation

@FloSch62

@FloSch62 FloSch62 commented Nov 7, 2026 •

Copy link
Copy Markdown
Member

Updates the direct and indirect Go modules to their latest releases, and pins containerlab to the v0.83.0 release.

Notable bumps

  • github.com/srl-labs/containerlab v0.83.0 (was a pre-release pseudo-version of v0.82.1)
  • github.com/shirou/gopsutil/v4 v4.26.10
  • go.yaml.in/yaml/v3 v3.0.6
  • github.com/clabernetes/clabernetes v0.11.0
  • k8s.io/apiextensions-apiserver / k8s.io/apiserver v0.37.2, which pulls github.com/google/cel-go v0.29.2
  • google.golang.org/grpc v1.85.0, golang.org/x/net v0.62.0
  • gin-contrib, sigstore, buildkit, moby/sys, go-jose, gopacket, etcd, genproto and other smaller updates

Held back

  • k8s.io/kube-openapi: the newest version needs structured-merge-diff/v7, which k8s.io/apimachinery v0.37.2 does not support yet.
  • cel-go v0.32: this release moved to the cel.dev/cel-go module path. v0.29.2 already fixes the advisory.

Security

Exec no longer holds the containerlab lock

Service.Exec held the server-wide containerlabMu for as long as the exec'd commands ran, so a long exec stalled every other lab operation until it returned. In CI this made TestCaptureStreamNeedsNoEdgeshark flaky: the capture waited behind the 6 s ping and then captured an idle link. The lock and the working directory now cover only loading the topology and listing the target containers.

SR Linux nodes report their management address again

containerlab v0.83.0 runs SR Linux nodes in the network namespace of an internal holder container (<node>-netns), as SR-SIM nodes already did. Docker reports no address, network or ports for a container that joins another's namespace, and the API hides the holders, so SR Linux nodes showed N/A and SSH access to them failed in CI. Container listings now give each such node its holder's network before the holders are hidden, including lookups by container name.

Testing

  • go build ./..., go vet ./... and go test ./internal/... pass.
  • Deployed an SR Linux node with containerlab v0.83.0 locally: before the fix the API listed it as N/A, after it as 172.20.20.2/24, for lab-wide listings and for the lookup by container name the SSH handler uses.

Closes #178
Closes #189
Closes #190

Update the direct and indirect Go modules to their latest releases,
except containerlab, which stays on its current pin until v0.83.0.

Notable bumps:
- github.com/shirou/gopsutil/v4 v4.26.10
- go.yaml.in/yaml/v3 v3.0.6
- github.com/clabernetes/clabernetes v0.11.0
- k8s.io/apiextensions-apiserver v0.37.2, which pulls
  github.com/google/cel-go v0.29.2 (fixes the open cel-go advisory)
- google.golang.org/grpc v1.85.0, golang.org/x/net v0.62.0

k8s.io/kube-openapi stays on its pin: the newest version needs
structured-merge-diff v7, which apimachinery v0.37.2 does not support yet.
Service.Exec held containerlabMu for as long as the commands ran, so a
long exec (a ping, a script) stalled every other lab operation on the
server until it returned. A capture started next to such an exec only
began once the exec finished, which made the capture stream test flaky.

The lock and the working directory are now held only while the topology
is loaded and the target containers are listed.
containerlab v0.83.0 runs SR Linux nodes in the network namespace of an
internal holder container, as SR-SIM nodes already did. The runtime
reports no address, network or published ports for a container that
joins another's network namespace, and the holders are hidden from
listings, so these nodes showed "N/A" and SSH access to them failed.

Listings now give each such node the network of its holder before the
holders are hidden. A listing filtered by container or node name does
not include the holders, so they are listed for the node's lab.

The SSH suite no longer takes "N/A" for an address while it waits for
its lab.
@FloSch62
FloSch62 merged commit 2dbc0d2 into main Nov 7, 2026
3 of 4 checks passed
@FloSch62
FloSch62 deleted the chore/bump-deps branch November 7, 2026 12:12
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.

1 participant