#linuxserverio — Public Fediverse posts

@spla jo estava esperant a veure si #linuxserverio treu alguna revisió de la imatge.

@spla jo estava esperant a veure si #linuxserverio treu alguna revisió de la imatge.

@spla jo estava esperant a veure si #linuxserverio treu alguna revisió de la imatge.

@spla jo estava esperant a veure si #linuxserverio treu alguna revisió de la imatge.

@spla jo estava esperant a veure si #linuxserverio treu alguna revisió de la imatge.

Trying to set up #mariadb using the #linuxserverio image on #kubernetes and it's not going well...

It's not picking up the root/user passwords I'm setting and at first I was willing to guess I messed up something so I scrapped the pod, pvc and pv and started fresh.

Then I noticed it was getting OOMKilled seconds after the pod first boots up. Great! Obviously, that affected the db set up and that's why I can't connect... Nope, increasing the pod memory didn't fix it

Read the LSIO docs again and noticed you don't need a password to sign into root (as long as you're using the OS root account.) Okay, I'm running the image as non-root user so maybe that explains why I can't sign in... But I need to do that because I'm storing db config on pvc backed by NFS which is picky about user access and it's easier to run stuff as a predictable non-root user... And NFS is the only reasonable option I currently have for dynamically provisioned storage which I need because I'm deploying MariaDB as a statefulset... Fuck

Trying to set up #mariadb using the #linuxserverio image on #kubernetes and it's not going well...

It's not picking up the root/user passwords I'm setting and at first I was willing to guess I messed up something so I scrapped the pod, pvc and pv and started fresh.

Then I noticed it was getting OOMKilled seconds after the pod first boots up. Great! Obviously, that affected the db set up and that's why I can't connect... Nope, increasing the pod memory didn't fix it

Read the LSIO docs again and noticed you don't need a password to sign into root (as long as you're using the OS root account.) Okay, I'm running the image as non-root user so maybe that explains why I can't sign in... But I need to do that because I'm storing db config on pvc backed by NFS which is picky about user access and it's easier to run stuff as a predictable non-root user... And NFS is the only reasonable option I currently have for dynamically provisioned storage which I need because I'm deploying MariaDB as a statefulset... Fuck

Trying to set up #mariadb using the #linuxserverio image on #kubernetes and it's not going well...

It's not picking up the root/user passwords I'm setting and at first I was willing to guess I messed up something so I scrapped the pod, pvc and pv and started fresh.

Then I noticed it was getting OOMKilled seconds after the pod first boots up. Great! Obviously, that affected the db set up and that's why I can't connect... Nope, increasing the pod memory didn't fix it

Read the LSIO docs again and noticed you don't need a password to sign into root (as long as you're using the OS root account.) Okay, I'm running the image as non-root user so maybe that explains why I can't sign in... But I need to do that because I'm storing db config on pvc backed by NFS which is picky about user access and it's easier to run stuff as a predictable non-root user... And NFS is the only reasonable option I currently have for dynamically provisioned storage which I need because I'm deploying MariaDB as a statefulset... Fuck

Trying to set up #mariadb using the #linuxserverio image on #kubernetes and it's not going well...

It's not picking up the root/user passwords I'm setting and at first I was willing to guess I messed up something so I scrapped the pod, pvc and pv and started fresh.

Then I noticed it was getting OOMKilled seconds after the pod first boots up. Great! Obviously, that affected the db set up and that's why I can't connect... Nope, increasing the pod memory didn't fix it

Read the LSIO docs again and noticed you don't need a password to sign into root (as long as you're using the OS root account.) Okay, I'm running the image as non-root user so maybe that explains why I can't sign in... But I need to do that because I'm storing db config on pvc backed by NFS which is picky about user access and it's easier to run stuff as a predictable non-root user... And NFS is the only reasonable option I currently have for dynamically provisioned storage which I need because I'm deploying MariaDB as a statefulset... Fuck

Shoutout to #linuxserverio and their CI providing up-to-date #mastodon #docker images in no time.

Shoutout to #linuxserverio and their CI providing up-to-date #mastodon #docker images in no time.

Shoutout to #linuxserverio and their CI providing up-to-date #mastodon #docker images in no time.

I wish #linuxserverio would make a #mastodonglitch container. Trying to setup from scratch with #docker is a huge pain...

I wish #linuxserverio would make a #mastodonglitch container. Trying to setup from scratch with #docker is a huge pain...

I wish #linuxserverio would make a #mastodonglitch container. Trying to setup from scratch with #docker is a huge pain...

I came across the #Fail2Ban #docker image from #linuxserverio and thought to myself that it's finally time to set up Fail2Ban. I admit i never used it before and it was a bit difficult to add it to my #playbook as all of my #servers have different services and therefore different #logfile paths, but that's nothing #jinja #templating can't fix.

Now that i've got #Discord notifications for banned #IPs, it's time to work on actual #IPblocking. I also want to use the #IPComplaint and #AbuseIPDB actions as i really like the idea of reporting abuse (even though i have no idea how effective that may be).

I may also want to replace the discord #webhook with #email notifications later as that's mostly the reason i've set up a #mailserver ( #stalwart ) in the first place.

I mean, most of my services are only accessible from #tailscale or my #homenetwork, but since #Ansible makes it so much easier to apply higher standards, i just can't resist. My #homelab is changing every day and i think setting up additional #security, even though i don't need it yet, is never a bad idea.

#networking #badactors #firewall #automation #linux #selfhosting #homeserver

I came across the #Fail2Ban #docker image from #linuxserverio and thought to myself that it's finally time to set up Fail2Ban. I admit i never used it before and it was a bit difficult to add it to my #playbook as all of my #servers have different services and therefore different #logfile paths, but that's nothing #jinja #templating can't fix.

Now that i've got #Discord notifications for banned #IPs, it's time to work on actual #IPblocking. I also want to use the #IPComplaint and #AbuseIPDB actions as i really like the idea of reporting abuse (even though i have no idea how effective that may be).

I may also want to replace the discord #webhook with #email notifications later as that's mostly the reason i've set up a #mailserver ( #stalwart ) in the first place.

I mean, most of my services are only accessible from #tailscale or my #homenetwork, but since #Ansible makes it so much easier to apply higher standards, i just can't resist. My #homelab is changing every day and i think setting up additional #security, even though i don't need it yet, is never a bad idea.

#networking #badactors #firewall #automation #linux #selfhosting #homeserver

I came across the #Fail2Ban #docker image from #linuxserverio and thought to myself that it's finally time to set up Fail2Ban. I admit i never used it before and it was a bit difficult to add it to my #playbook as all of my #servers have different services and therefore different #logfile paths, but that's nothing #jinja #templating can't fix.

Now that i've got #Discord notifications for banned #IPs, it's time to work on actual #IPblocking. I also want to use the #IPComplaint and #AbuseIPDB actions as i really like the idea of reporting abuse (even though i have no idea how effective that may be).

I may also want to replace the discord #webhook with #email notifications later as that's mostly the reason i've set up a #mailserver ( #stalwart ) in the first place.

I mean, most of my services are only accessible from #tailscale or my #homenetwork, but since #Ansible makes it so much easier to apply higher standards, i just can't resist. My #homelab is changing every day and i think setting up additional #security, even though i don't need it yet, is never a bad idea.

#networking #badactors #firewall #automation #linux #selfhosting #homeserver

I came across the #Fail2Ban #docker image from #linuxserverio and thought to myself that it's finally time to set up Fail2Ban. I admit i never used it before and it was a bit difficult to add it to my #playbook as all of my #servers have different services and therefore different #logfile paths, but that's nothing #jinja #templating can't fix.

Now that i've got #Discord notifications for banned #IPs, it's time to work on actual #IPblocking. I also want to use the #IPComplaint and #AbuseIPDB actions as i really like the idea of reporting abuse (even though i have no idea how effective that may be).

I may also want to replace the discord #webhook with #email notifications later as that's mostly the reason i've set up a #mailserver ( #stalwart ) in the first place.

I mean, most of my services are only accessible from #tailscale or my #homenetwork, but since #Ansible makes it so much easier to apply higher standards, i just can't resist. My #homelab is changing every day and i think setting up additional #security, even though i don't need it yet, is never a bad idea.

#networking #badactors #firewall #automation #linux #selfhosting #homeserver

I came across the #Fail2Ban #docker image from #linuxserverio and thought to myself that it's finally time to set up Fail2Ban. I admit i never used it before and it was a bit difficult to add it to my #playbook as all of my #servers have different services and therefore different #logfile paths, but that's nothing #jinja #templating can't fix.

Now that i've got #Discord notifications for banned #IPs, it's time to work on actual #IPblocking. I also want to use the #IPComplaint and #AbuseIPDB actions as i really like the idea of reporting abuse (even though i have no idea how effective that may be).

I may also want to replace the discord #webhook with #email notifications later as that's mostly the reason i've set up a #mailserver ( #stalwart ) in the first place.

I mean, most of my services are only accessible from #tailscale or my #homenetwork, but since #Ansible makes it so much easier to apply higher standards, i just can't resist. My #homelab is changing every day and i think setting up additional #security, even though i don't need it yet, is never a bad idea.

#networking #badactors #firewall #automation #linux #selfhosting #homeserver

@techviator Big fan of disposable browsers. Been using the mullvad-browser image from #linuxserverio for some time now and love it. It's very useful in certain situations.

@techviator Big fan of disposable browsers. Been using the mullvad-browser image from #linuxserverio for some time now and love it. It's very useful in certain situations.

@techviator Big fan of disposable browsers. Been using the mullvad-browser image from #linuxserverio for some time now and love it. It's very useful in certain situations.

@techviator Big fan of disposable browsers. Been using the mullvad-browser image from #linuxserverio for some time now and love it. It's very useful in certain situations.

@techviator Big fan of disposable browsers. Been using the mullvad-browser image from #linuxserverio for some time now and love it. It's very useful in certain situations.