On Mon, Feb 4, 2019 at 4:01 PM Erik McCormick <emccormick at cirrusseven.com> wrote: [snip detailed helpful stuff] The really dirty but useful way to test small changes would be to just push > them into the container with 'docker cp' and restart the container. Note > that this will not work for config changes as those files get clobbered at > startup, but for hacking the actual python bits, it'll do. > This was news to me to be honest. I had assumed the container filesystem got reset on process restart, but you're right and that's not true. So, editing files in the container works for my current needs. Thanks heaps! Michael -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190204/f9b832d6/attachment.html>