kube play with sdnotify=conmon: Error: Closing notify proxy: close unixgram: use of closed network connection

[edsantiago]

$ cat >/tmp/foo.yaml <<EOF
apiVersion: v1
kind: Pod
metadata:
  labels:
    app: test
  name: test_pod
  annotations:
    io.containers.sdnotify: conmon
spec:
  restartPolicy: Never
  containers:
    - name: ctr1
      image: quay.io/libpod/testimage:20221018
      command:
      - true
EOF
$ bin/podman kube play /tmp/foo.yaml
ERRO[0001] Closing notify proxy "/dev/shm/-podman-notify-proxy.sock146894828": close unixgram /dev/shm/-podman-notify-proxy.sock146894828: use of closed network connection 
Pod:
2c0e114741a88f943b8483f56e57d604620cd12c03334080e3a9ea92555a1246
Container:
ade31f15fdc15685d03586067948d1d2d5a5c1e11c90938e5484f6050b9680d2

100% reproducible on my f38 laptop, not a flake. This is the source of the .sock file:

podman/pkg/systemd/notifyproxy/notifyproxy.go

Lines 66 to 69 in 7bd6086

	// New creates a NotifyProxy that starts listening immediately. The specified
	// temp directory can be left empty.
	func New(tmpDir string) (*NotifyProxy, error) {
	tempFile, err := os.CreateTemp(tmpDir, "-podman-notify-proxy.sock")

[vrothberg]

Will look into it, thanks @edsantiago !

[vrothberg]

This really only works with --service-container. I will reflect a bit more on it tomorrow with a less fried brain #toohot

[edsantiago]

I'm not sure how to parse "only works" (maybe "should only work with --service-container", or "currently only work with ..."?). Anyhow, adding --service-container makes no difference. Same warning/error message. (This was discovered by accident in the "propagation" test in 260-sdnotify.bats, which always runs with --service-container).

And, this can wait. Stay cool.

[edsantiago]

git-bisect identifies #16709 as the culprit, which is unsurprising since that's where the "Closing notify proxy" message came in.

[vrothberg]

Opened #19727