Skip to content

Checklist for starting containers

  • hosting
  • server
  • servers
  • infrastructure
  • docker
  • podman
  • containers
  • edge

The problem

I'm a total noob scrub and need to learn containers to compete in the realm of containers.

The solution

    • make a VM, it doesn't need a desktop, but you need to access it.
      • bonus points if you only use ssh keys and no passwords.
    • install a container execution engine
    • docker - the defacto noob standard.
    • podman - the steriod version of docker but more unix than docker.
  1. use it.
    1. to launch other peoples works
    2. to launch our own works
    • setup orchestrator to control the program and build an entire flippin system around it.
      • Install and run omni locally.
        • docker
        • podman
        • [✔️] kubernetes
        • other
      • AWS GOOGLE Omni ...
        • Secu
    • Container orchistrator is setup, now orchistrate a container.
    • Build a container that does the bear freaking minimum so you can understand or something or not the world is annoyingling just snarky and shit.

Crapware

1. My experience:
    1. setup a NAS
        * computer with stuff
        * install proxmox
        * add drives
        * download NAS software with UI that wasn't half bad that was available at time.
        * installed proxmox first, passed through hdd control to truenas and added a bunch of sick sweet drives
        * setup drives with ZFS and duplication and stuff etc mostly gigantic 14+TB hdd's
    2. Refine the NAS
        * add ceph to the proxmox cluster
        * move the nas to the ceph, all data will be replicated on a minimum of (x) machines
        * encryption is enabled by default and keystore is .. 
            * vault?
            * depends on how hard it matters now or ever which when compared with ever it's always basically equal to zero
    3. Creating the kubernetes
        * Omni .. a haven.
            * Talos nodes.
            * it takes an hours to reboot but it shouldn't, honestly
            * One node went offline, some serives were still on and others were not. 
                * Not cool. All services need to run regardless.