Mathias Fredriksson df92df4565 fix(agent): filter out GOTRACEBACK=none (#16924) ...

With the switch to Go 1.24.1, our dogfood workspaces started setting
`GOTRACEBACK=none` in the environment, resulting in missing stacktraces
for users.

This is due to the capability changes we do when
`USE_CAP_NET_ADMIN=true`.

https://github.com/coder/coder/blob/564b387262e5b768c503e5317242d9ab576395d6/provisionersdk/scripts/bootstrap_linux.sh#L60-L76

This most likely triggers a change in securitybits which sets
`_AT_SECURE` for the process.

https://github.com/golang/go/blob/a1ddbdd3ef8b739aab53f20d6ed0a61c3474cf12/src/runtime/os_linux.go#L297-L327

Which in turn triggers secure mode:

https://github.com/golang/go/blob/a1ddbdd3ef8b739aab53f20d6ed0a61c3474cf12/src/runtime/security_unix.go

This should not affect workspaces as template authors can still set the
environment on the agent resource.

See https://pkg.go.dev/runtime#hdr-Security

2025-03-17 11:10:14 +02:00

..

usershell_darwin.go

feat(agent): add second SSH listener on port 22 (#16627)

2025-03-03 04:47:42 +01:00

usershell_other.go

feat(agent): wire up agentssh server to allow exec into container (#16638)

2025-02-26 09:03:27 +00:00

usershell_test.go

fix(agent): filter out GOTRACEBACK=none (#16924)

2025-03-17 11:10:14 +02:00

usershell_windows.go

feat(agent): wire up agentssh server to allow exec into container (#16638)

2025-02-26 09:03:27 +00:00

usershell.go

fix(agent): filter out GOTRACEBACK=none (#16924)

2025-03-17 11:10:14 +02:00