Yeah, that would be my recommendation too. Anything else will produce a worse experience (laggy and slow) and more complexity to get setup/maintain.

Some of the commands I use a lot for debugging containers, in case you go down that route:

• docker run --rm -it --entrypoint bash <image_name>
• This command let’s you enter a docker image with bash so you can test commands and treat it like a temporary VM. Great way to see how the image is setup
• docker exec -it <container_name>
• This let’s you enter a running container with bash. A great way to inspect why something might not be working or check mounted volumes, etc.

Once you know how to use docker/containerization it’ll be the only way you want to deploy applications. Most popular applications will also have good guides on how to setup/config the container, but sometimes you’ll need to read up on docker and Linux to figure things out.