Gruß Hartmut

Why don't you share it here? I'm curious...

contact me i can protect your streams allow only domain names you want
+212667400457
TG: @lamadya

I'm sorry but somehow I missed it that this comment was still awaiting approval. I'm ready when you are!

Hi A I am ready to do this after upgrading my network and making it more stable. let me know when your ready, I will syndicate this from your site and on my forum https://forum.diode.io you can see my posts on various blockchain services with embedded devices and private cloud infrastructure. look forward to doing this finally

awesome

I dont blame you its a rabbit hole. I ran your script on a clean VM and it works great

Hi A,

awesome lets collaborate over a video teams conf, I can send the invite and we can work through how to do the workflow, this will be a great post and will blow up your blog, I guarantee it. with your automation capability and my testing blockchain it will be great.

To be honest I have never really delved in what you call lxc terrirory. So this all is new to me. I'll need to dive into this before I completely understand (thats because of how my brain is wired).
I will look into this because I'm always interested in things I have no knowledge of yet. I'm afraid I'm not confident enough at this moment to answer your last question. But I'll get back to you when I do.

Great idea 🙂 And I already did. It will now stop the script and display an error that something went wrong with installing snap. Right before the step where it creates the symlink for snap.

That's an interesting idea. I'd be very Ok with creating an account for you on this website so you can write posts on the subject. That would actually be really great! Perhaps we should handle the details via email to make this happen?

Ok I dug further into lxc territory and found that you have to enable nesting in an unprivileged container

- For unprivileged containers:
1) Put this in /etc/pve/lxc/vmid.conf: (change to the vmid like 100.conf)
Code:
...
features: mount=fuse,nesting=1
lxc.mount.entry = /dev/fuse dev/fuse none bind,create=file 0 0
2) Inside the container: `apt install squashfuse`

- For privileged containers, also add:
Code:
...
# EDIT:
# We need to allow apparmor administration, by default mac_admin is dropped for privileged containers.
# Note that you do not want this for un-trusted containers...
lxc.cap.drop =
lxc.cap.drop = mac_override sys_time sys_module sys_rawio
Alternatively to squashfuse, privileged containers could use loop devices, but I wouldn't recommend it...

Note that enabling `fuse` in a container does not play well with backups, or anything that causes an `lxc-freeze` command to be executed on the container, as this can cause deadlocks in the kernel...

how to force a reinstall of everything or reset it to run the script again?

root@media-server:~# snap
Command 'snap' not found, but can be installed with:
apt install snapd
root@media-server:~#
bingo, maybe add in your script a check for snap as a dependency?

I think snap wasnt available on the lxc thats where it craps out. Good catch and hope it reduces complaints or issues. I have forked your script and will look to add in the blockchain stuff, it will take some working through. I would love to then make a joint blog here in ustoopia to create a series of how people can decentralise a lot of stuff.

That's something I didn't come across during testing. The script does clearly install certbot using snap. Is this perhaps where things went wrong for you?
This is what is in the script, and should make it work in any cases:

# Install Snap core first so we can then install Certbot
sudo snap install core; sudo snap refresh core
sudo snap install --classic certbot
# Create a link to certbot so we can use it later on
sudo ln -s /snap/bin/certbot /usr/bin/certbot

But since you pointed this out, I've added a couple of lines to the script that will check to see if certbot was installed or not.

# Check if certbot command exists (indicating successful installation)
if ! command -v certbot &> /dev/null; then
echo "Error: Certbot was not installed properly. Exiting."
exit 1
fi

just one thing I noticed on a virgin ubuntu lxc with no certbot ti complains of sudo: certbot: command not found