set tracing socket path to runtime dir#4078
Conversation
|
|
||
| func traceSocketPath(root string) string { | ||
| return filepath.Join(root, "otel-grpc.sock") | ||
| func traceSocketPath(inUserNS bool) string { |
There was a problem hiding this comment.
This should be moved to https://github.com/moby/buildkit/blob/master/util/appdefaults/appdefaults_unix.go
|
In rootless mode in our integration tests that sounds legit:
Added |
Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com>
|
Hum it still tries to write to xdg runtime dir in rootless mode for frontend integration tests, I might miss smth: https://github.com/moby/buildkit/actions/runs/5716370920/job/15487868441?pr=4078#step:7:1143 Edit: I think we are losing env context with sudo, I will take a look. |
Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com>
tonistiigi
left a comment
There was a problem hiding this comment.
I'm not sure if this is completely safe to pick to v0.12 . Maybe there are some weird perm errors for /run/buildkit in some systems.
How about we merge this for master and pick https://github.com/moby/buildkit/pull/3483/files for v0.12?
Fine to me |
| } | ||
| // TODO: make sure the user exists and subuid/subgid are configured. | ||
| buildkitdArgs = append([]string{"sudo", "-u", fmt.Sprintf("#%d", s.UID), "-i", "--", "exec", "rootlesskit"}, buildkitdArgs...) | ||
| buildkitdArgs = append([]string{"sudo", "-E", "-u", fmt.Sprintf("#%d", s.UID), "-i", "--", "exec", "rootlesskit"}, buildkitdArgs...) |
There was a problem hiding this comment.
@crazy-max looks like this actually disables all the rootless tests 👀
See https://github.com/moby/buildkit/actions/runs/5749062460/job/15583230313:
time="2023-08-03T09:40:23Z" level=warning msg="rootless mode is not supported on this host: exit status 1 (sudo: you may not specify both the -i and -E options\nusage: sudo -h | -K | -k | -V\nusage: sudo -v [-ABkNnS] [-g group] [-h host] [-p prompt] [-u user]\nusage: sudo -l [-ABkNnS] [-g group] [-h host] [-p prompt] [-U user] [-u user]\n [command [arg ...]]\nusage: sudo [-ABbEHkNnPS] [-C num] [-D directory] [-g group] [-h host] [-p\n prompt] [-R directory] [-T timeout] [-u user] [VAR=value] [-i | -s]\n [command [arg ...]]\nusage: sudo -e [-ABkNnS] [-C num] [-D directory] [-g group] [-h host] [-p\n prompt] [-R directory] [-T timeout] [-u user] file ...\n)"
There was a problem hiding this comment.
yikes test step didn't failed 😕
There was a problem hiding this comment.
|
Removing from the v0.12.1 milestone, see #4078 (comment). |
fixes #4036