21
submitted 2 months ago* (last edited 2 months ago) by iturnedintoanewt@lemm.ee to c/selfhosted@lemmy.world

Hi guys!

Back in the day I used to have a VM holding nginx and all the crap exposed...and I did set it up with fail2ban. I moved away from it, as the OS upgrade was turning messy, and rebuilt onto an LXC container. How should I use fail2ban/iptables in order to protect/harden my LXC container/server? Do the same conditions apply, or will I have any limitations/issues due to the container itself?

Thanks!

you are viewing a single comment's thread
view the rest of the comments
[-] 486@lemmy.world 5 points 2 months ago* (last edited 2 months ago)

No, it is not like Docker. You can treat an LXC container pretty much like a VM in most instances, including firewall rules. To answer the question, you can use fail2ban just like you had done in your VM, meaning you can run it inside the LXC container, where fail2ban can change the firewall rules of that container as it sees fit.

[-] iturnedintoanewt@lemm.ee 1 points 2 months ago

Thanks I appreciate your reply... I have a bit of concern about an unprivileged container having firewall limitations (as I might have read in the past this was...finicky), but I'm going to give it a shot.

[-] 486@lemmy.world 3 points 2 months ago

I'm exclusively running unprivileged LXC containers and haven't had any issues regarding the firewall, neither with iptables nor nftables.

[-] K3can@lemmy.radio 3 points 2 months ago

I've also been running nginx in an unprivileged LXC container. I haven't used fail2ban, specifically, but crowdsec has been working without issue.

You can mostly just treat an LXC like a normal VM.

this post was submitted on 09 Sep 2024
21 points (95.7% liked)

Selfhosted

39677 readers
160 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS