There's nothing really wrong with what you're doing. Apps were deployed like that for decades before docker came along. To my mind the main benefit of containe

There's nothing really wrong with what you're doing. Apps were deployed like that for decades before docker came along. To my mind the main benefit of containerization would be that the > binary, config files and static assets would be bundled together inside the container, so there is less risk of you running a half-baked version where (e.g.) the binary gets updated but the other files don't. However since you're using Ansible to deploy, that risk already feels small. You could also consider using the embed feature in go1.16 to bundle all the assets inside the binary. Arguably there might also some security benefit to running in a container, but I wouldn't want to try and make that argument without knowing a lot more about the specific details of your binary's behaviour.