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

help-circle


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






  • I can only speak to what’s expected in the US.

    For personal info you should include your full legal name, a contact phone number, email, and possibly a link to a portfolio of some kind if that’s expected in your industry (arts, software, design, etc.). No need to put a birth date or any more personal info. If you’re applying to work in another country, I would indicate your nationality and what visas you might have or need to be sponsored for.

    For education, just put the institution, degree, field of study, location, and dates. You can include degree honors there if you have any. Once you have an undergrad degree of some kind, you can remove your high school unless its particularly prestigious.

    After that it should primarily be a list of any work experience, notable projects, skills, and honors/awards.




  • As I understand it, NAT is a firewall with only a very basic configuration: allow all outbound and accept only established inbound. If you don’t expect to have any incoming connections and completely trust all your internal devices then its good enough.

    However, if you start wanting to port forward for servers (SSH, FTP, video games) you need to poke holes in the NAT firewall and it has no additional configuration options to help you. The same goes for if you have internal (ex. IoT) devices that you don’t necessarily trust, there are no rules to block outbound traffic.




  • I wonder what the risks are to including deleted and pre-edited content in training data. Most of the edits are going to be typos and formatting, do you want 2-3 copies of the same message with typos in them for training data? Similarly, deleted comments are mostly nonsense, unhelpful, duplicate, or highly controversial things.

    If someone wants to dig through and find individual users to restore that’s one thing, but I don’t think I’d immediately choose to train off of that other data unless I had to.