I totally missed this topic while I sought to do the same over the last few days.
I had a different goal in mind (for development). I wanted to run a full test network within the container plus a pre-authorized CLI.
One challenge I struggled with is the networking part. I resorted to --network=host, which causes the container to have full access to the network interface of the host and thus allowing the nodes/network to function and communicate with local clients. I could not get it to work without it. But, I just found out Windows does not support --network=host (actually only Linux).
Perhaps someone more enlightened than me can chime in with possible solutions. Instead of --network=host I tried --publish 127.0.0.1:12000-12011:12000-12011/udp. I run all the nodes on port 12000 to 12011, so I assumed the network was then accessible on the host, but clients can’t connect. I don’t know enough about bootstrapping/networking to see what is wrong or how to fix it.