fabricionaweb

This thread is nice because seems no one is really reading each other messages hahahahah But thanks everyone, it still have some nice insights

The OP's post is old and I feel like some info can be added. - Do not just install random packages on your machine - After Unraid 6.12.0 the OpenSSL included is already 1.1.1 - Python is included in Slackware, dont need to look elsewhere for the .SlackBuild recipe. You can just get it from the official mirrors - Slackware64 (amd64 or x86_64) is what you look for, and there are two branches: stable (15.0) and the current (testing) At time I post this: - "15.0" (Unraid 6) you get the Python 3.9.19 due security patches - "current" (Unraid 7 afaik, I havent tested) you get the Python 3.11.9 Both has sources (the .SlackBuild) and .txz packages available there. Problem is: it is not a static build, it share .so dependencies and if you just grab a build from "current" to install on "15.0" it will not always work... or may not worth try to fix the whole dependency tree... you can end broken something else. Another observation is that pip3 (and setuptools) isnt include by default, you can just install both by simple running "python3 -m ensurepip" but it needs to run again after every install (or reboot) in case of Unraid (not a big deal actually). This is upstream decision due pip being a separated project. Although the source is just there for you to do what is needed for each particular case... Like ours. Grab the "current" .SlackBuild and build it against the "15.0" most of the dependencies will probably be correct. I have build the 3.11.9 (and 3.12.5) from the official recipe (with few changes) on a Slackware-15 LXC (all my love to @ich777's plugin) and it seems to work just fine. glibc and openssl all linked correct within Unraid 6. You dont need (neither want to) be installing openssl3 glibc or anything else... I have made a document within the steps I followed if someone wants to build it: https://gist.github.com/fabricionaweb/95c84ba87710c781330b8842efafd0b1

You dont need the `incomplete` since its resides inside the `usenet` already, grep will capture both anyway (the start path is the same, its match) The command just uses `grep` with `-v` to filter (removing) the matched from the result, combined with `-F` to literal string (no regex) and `-f` to specify the file that contains one pattern (in this case literal string only) per line. See grep man https://man7.org/linux/man-pages/man1/grep.1.html Test mode would run something like `find "/mnt/cache_downloads/data" | grep -vFf '/mnt/user/backups/ignore-files.txt'`

I dont want to say something wrong here... I'd prefer to wait they to fix it or provide a way to do it, sorry. The only way I know is to install the package outside nerdtools and I can not advise it here.

I have running experiments and seems that I got it. As far as it concern to security, to the mount points, those /dev /proc stuffs, Im really dont not know much, so I can not review it or say nothing about it. Yet Im testing. But I have already found some particularities: - For this container the mac address in the config file does not work, so we just dont add it. It seems like the Slackware has they things about it. But just enabling DHCP worked. Every reboot has a new MAC but I think I can change it in some Slackware way. - It was missing some packages in the container to be able to run gpg signatures and the repository, so I added. After install two packages on Unraid (slackpkg and gnupg) I could build the container fine :tada: If you want see what I have done, I made a small documentation about it (git history mostly) https://github.com/fabricionaweb/lxc-slackware I have not done my things yet inside the container, its early to say much. But the container is running. -- update Just a heads up, after one small issue in the container (about the gpg), I ran `update-ca-certificates --fresh` to fix. Installed dependencies and already building the packages I wanted just fine. I think its working

I was thinking in having a container for development and build some packages when needed. Maybe I do some backups first and try to compile that template later. Or maybe I just go VM

Does someone knows how to create a slackware container? I googled a lot, I found some stuff, one lxc-template, but Im not confident enough to run it... I prefer to ask first

I figured out the last python build `python3-3.9.16-x86_64-3` was built without ssl. The previous build `python3-3.9.16-x86_64-1` works fine. I tested both here.

Just a feedback, I have been using it for a while already, months I think, and It have been such a good experience! Im running 6 containers (2 debian 4 alpine), 4 of them is production (1 debian 3 alpine). Everything running amazing well and smooth... I really love and appreciate the work you have bring to Unraid. It is an incredible experience to use it. Only thing that may have bother me is the user mapping, since it is root some containers may "conflict" users/groups, but I have moved those to 1000, so if you know what you are doing you will be fine! Thanks!!!

I need to say the urls are outdated giving 404... Forum's url changed

Is it possible to create unprivileged containers?

What I've investigate so far, out of curiosity, and I may be wrong, cause I learned it today: - although github registry works with both: Registry v2.2 and Open Container Initiative (OCI) - seems like some Docker images are only with Open Container (and I dont know why or how this works), the webgui is sending the Accept header only for Registry 2.2 (see the docs) - the changes in this thread is to add the Accept header for Open Container Initiative (see the docs) That was my 2cents, hope it help to understand

Good catch, I also saw there was an issue since June 2022. I hope you dont mind but I opened the MR and also added some references. Thank you to figued out!

If I remove the `dev` from `wg0.conf` I can not turn active the vpn, it keeps under inactive state. Removing both `dev wg0` I could at least turn wireguard on, but did not worked as well. I have handshake and some lan connection but really nothing else works. I can confirm it was working before upgrade in the really same configs. -- edit Ok I got mine to work and I did not need to change wg0.conf. Im not sure what worked because I did many things, but there is two or three settings that I can suspect. What I did: - stopped the wireguard if it was running - deleted some docker network like br0 and wg0 - stopped docker network - disabled "Host access to custom networks" in Docker settings - uncheck the "IPV4 Custom network on interface br0" yet in Docker settings - reboot My wg0.conf still have the `dev br0` and `dev wg0` but it is working now.