Follow up report: so, I sort of did that, but not, since a) I’m not using VSCode and I’m learning enough other junk at the moment I didn’t want to get involved and b) reworking the docker-compose and Dockerfile wasn’t working out cleanly. So, what I’ve done is write a small shell script to type all that verbose docker junk so I don’t fat finger it or get it wrong. Then, another one which I source when the container spins up, which exports all the environment variables my server expects to have, to run properly (normally specified in docker-compose.yml). Then, *another* one which runs the build and then copies all the artifacts into a working directory and runs the server. And it works! Sweet!

Now, of course, I’m discovering that there’s a segfault somewhere in the server framework at shutdown, and it happens sometime after my code is done, so I guess I don’t care too much…except that now I wonder where all the blasted core files are going.