• 0 Posts
  • 48 Comments
Joined 11 months ago
cake
Cake day: October 19th, 2023

help-circle

  • VOY 3x8,3x9,3x10,3x11, and 3x12. I haven’t seen Voyager since it originally aired and my partner has never seen it. This is a really interesting point in the series for me.

    The good: the doctor gets the mobile emitter. This is the first really big change in the show structure and more doctor is always better. Plus, Future’s End (3x8 and 3x9) is a really fun 2-parter with great guests.

    The bad: the lack of character or circumstance development really starts to drag by this point. I know there’s the big shakeup at the end of season 3 and I’m extremely ready for it. Warlord (3x10) tries to be a big Kes episode to circle back to her psychic powers but like everything it goes nowhere. Not to mention I know her story goes nowhere so it’s hard to be excited about anything she does.















  • You can absolutely do this without polluting anything on your system.

    The directory name doesn’t matter, when you build the image you’ll specify a tag for it.

    The only thing to watch for is when you build the same tag name again, as you iterate on the Dockerfile changes, docker won’t remove the old image from your local registry. It will just untag it, so you might see several images called something like “<None>”. Remember to remove those every so often so you don’t fill up your Pi’s storage.

    Edit: Also Docker will keep a “build cache” for this stuff, which doesn’t really “pollute” anything but it does take up disk space. You can clean that up with docker builder prune, read this for all the usage info: https://docs.docker.com/reference/cli/docker/builder/prune/



  • First, you’ll need to pick a base image. There are lots to choose from and what you choose will entirely depend on what this service is. NodeJS, python, php, java, etc, all have really solid base images that I would recommend working from. If none of those frameworks apply then you’ll need to work from an OS base image like debian or alpine. I highly recommend debian:stable-slim if you go this route.

    My recommendation is to then spin up a container of your base image and do the install of your service manually, taking careful notes of all your steps. If anything breaks, just blow it up and start again. Once you have all your steps you’ll need to convert that list into a Dockerfile. Go step by step and learn how to do each thing from the docs. Then you can build the image from the Dockerfile and upload to docker hub or anywhere else.