Ok, I had made some stupid vi errors and had a couple missing characters at the beginning of 40-udp-proxy-2020.sh and udp-proxy-2020.conf. I think I fixed those. Now when I run /mnt/data/on_boot.d/40-udp-proxy-2020.sh I simply get the response d5d30d3462df03298486167bc5220e78ca0f75ecde5e7471fceea866d693ace7
However, when I run podman ps all I get is:
podman ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
f3f508478663 localhost/unifi-os:latest /sbin/init 2 weeks ago Up 2 weeks ago unifi-os
Sorry for the n00b questions, I’m using a lot of tools I either have never used or which I haven’t used in more than a decade. (Using vi on my UDM was hilarious. My son thought I was hurt I was yelling so much.)
EDIT: I did manage to figure out a bit more about podman, and when I tried to get history I can see that (a) the container name does correspond to an image, and (b) there’s an issue getting any history for it because the “layer is not known”… Realize this is basically docker/podman debugging, but I just don’t know these tools. Thanks.
# podman history udp-proxy-2020
Error: error getting history of image "udp-proxy-2020": error getting image configuration for image "4a642e78ff5649447532caefa78aea05858ca4bbed11e44be2858704660165ec": error reading image "4a642e78ff5649447532caefa78aea05858ca4bbed11e44be2858704660165ec": layer not known
And in case this is useful, podman does believe that there is an image for udp-proxy-2020, but there is clearly another error with the images:
# podman images
ERRO[0000] error checking if image is a parent "4a642e78ff5649447532caefa78aea05858ca4bbed11e44be2858704660165ec": error reading image "4a642e78ff5649447532caefa78aea05858ca4bbed11e44be2858704660165ec": layer not known
REPOSITORY TAG IMAGE ID CREATED SIZE R/O
localhost/unifi-os latest be4d69174995 7 weeks ago 1.82 GB true
localhost/unifi-os default be4d69174995 7 weeks ago 1.82 GB true
docker.io/synfinatic/udp-proxy-2020 latest 914d21726ae4 7 months ago 12.9 MB false
localhost/unifi-os current 4a642e78ff56 10 months ago unable to determine size false
And, since I’m now in the business of trying to figure out tools I don’t understand, here’s one more thing to diagnose what’s going on:
# podman image tree docker.io/synfinatic/udp-proxy-2020
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x28 pc=0x1032f80]
goroutine 1 [running]:
github.com/containers/libpod/libpod/image.GetLayersMapWithImageInfo(0x40000c3310, 0x7fd14cde77, 0x23, 0x400034a430)
libpod-v1.6.1/vendor/src/github.com/containers/libpod/libpod/image/image.go:1468 +0x4f0
github.com/containers/libpod/pkg/adapter.(*LocalRuntime).Tree(0x400006fc20, 0x2b1f860, 0x40002f4c00, 0x400006fc00, 0x0, 0x0, 0x4000375700)
libpod-v1.6.1/vendor/src/github.com/containers/libpod/pkg/adapter/images.go:19 +0x78
main.treeCmd(0x2b1f860, 0x0, 0x0)
libpod-v1.6.1/vendor/src/github.com/containers/libpod/cmd/podman/tree.go:59 +0xb8
main.glob..func63(0x2abab20, 0x40003f4da0, 0x1, 0x1, 0x0, 0x0)
libpod-v1.6.1/vendor/src/github.com/containers/libpod/cmd/podman/tree.go:33 +0xb4
github.com/containers/libpod/vendor/github.com/spf13/cobra.(*Command).execute(0x2abab20, 0x40000be070, 0x1, 0x1, 0x2abab20, 0x40000be070)
libpod-v1.6.1/vendor/src/github.com/containers/libpod/vendor/github.com/spf13/cobra/command.go:826 +0x328
github.com/containers/libpod/vendor/github.com/spf13/cobra.(*Command).ExecuteC(0x2abc420, 0x6, 0x16fa37d, 0x8)
libpod-v1.6.1/vendor/src/github.com/containers/libpod/vendor/github.com/spf13/cobra/command.go:914 +0x230
github.com/containers/libpod/vendor/github.com/spf13/cobra.(*Command).Execute(...)
libpod-v1.6.1/vendor/src/github.com/containers/libpod/vendor/github.com/spf13/cobra/command.go:864
main.main()
libpod-v1.6.1/vendor/src/github.com/containers/libpod/cmd/podman/main.go:160 +0xbc