I feel like if that’s something you’re doing, you’re using containers wrong. At least docker ones. I expect a container to have no state from run to run except what is written to mounted volumes. I should always be able to blow away my containers and images, and rebuild them from scratch. Afaik docker compose always implicitly runs with --rm for this reason.
- 1 Post
- 5 Comments
teawrecks@sopuli.xyzto
Selfhosted@lemmy.world•Frigate NVR Critical RCE VulnerabilityEnglish
2·6 days agoJust answering the question you asked.
teawrecks@sopuli.xyzto
Selfhosted@lemmy.world•Frigate NVR Critical RCE VulnerabilityEnglish
71·6 days agoSo they could view their cameras while they’re away?
teawrecks@sopuli.xyzto
Selfhosted@lemmy.world•How do I avoid becoming one with the botnet?English
1·9 days agoStep 1 is to do everything inside your network with data you don’t care about. Get comfortable starting services, visiting them locally, and playing around with them. See what you like and don’t like. Feel free to completely nuke everything and start from scratch a few times. (Containers like Docker make this super easy).
Step 2 is to start relying on it for things inside your network. Have a NAS, maybe home assistant, or some other services like Immich or Navidrome. Figure out how to give services access to your data without relying on them to not harm it (use read only mounts, permissions, snapshots, etc.)
Step 3 is to figure out how to make services more accessible away from home. Whether that is via a VPN, or something like tailscale, or just carefully opening specific ports to specific secure and up-to-date services. This is the part you’re feeling anxious about, and I think you’ll feel less anxious if you do steps 1 and 2 first and not even think about 3 yet. Consider it its own challenge, and just do one challenge at a time.
I just use gimp, but for the record, someone recently got modern Photoshop working in wine