• 0 Posts
  • 385 Comments
Joined 2 years ago
cake
Cake day: July 18th, 2023

help-circle
  • Yep, bind mount the data and config directories and back those up. You can test a backup by spinning up a new container with the data/config directories.

    This is both easy and generally the recommended thing I’ve seen for many services.

    The only thing that could cause issues is breaking changes caused by the docker images themselves, but that’s an issue regardless of backup strategy.







  • Yeah, but sizing is user dependent. So unless it’s based on the users purchasing history it’s useless what the average person does.

    If it said “L is your recommended size based on your purchase habits and customer data”, then sure. But it just says we recommend L because that’s what other people said/ordered, which makes no sense.






  • 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.