SELECT
‘#bicycle 🚴♂️’
,‘#databases’
,‘#sql’
,‘#selfhosting’
,‘#Linux 🐧’
,‘Team vi’
,‘#mdRzA’
,‘Generation X’
FROM life
WHERE 0 = 0
;
An “old” PC with an i7-4790T and 32 GB RAM.
I have also some Odroid devices based on 32bit-ARM.
But 32bit-ARM has the problem, that meanwhile many container images doesn’t support this architecture anymore.
So, when your Pi is already 64bit-ARM it could be ok.
Otherwise the possible selection regarding available prepared container images may be smaller.
@rtxn Maybe you find the reason in the chapter for Bridged Networking.
https://www.virtualbox.org/manual/ch06.html#network_bridged
With bridged networking, Oracle VM VirtualBox uses a device driver on your host system that filters data from your physical network adapter. This driver is therefore called a net filter driver. This enables Oracle VM VirtualBox to intercept data from the physical network and inject data into it, effectively creating a new network interface in software.
@rtxn I’m no expert in networking with VirtualBox, but did you already had a look into the manual?
https://www.virtualbox.org/manual/ch06.html#network_udp_tunnel
Das Schild “Gehwegschäden” ist auch sehr passend dazu.
🙃
Maybe you have to check Volume and Port settings, so that it fit your needs.
I always prefix my containers with “con-”, so that it is easier to finding them with systemctl --user.
[Container]
AutoUpdate=registry
ContainerName=con-portainer
HostName=con-portainer
Image=docker.io/portainer/portainer-ce:lts
Notify=conmon
PublishPort=8000:8000
PublishPort=9443:9443
Pull=missing
Volume=vol-portainer:/data
Volume=%t/podman/podman.sock:%t/podman/podman.sock
@Excaliburr Yes, you are right.
Do you have already a single container running with rootless podman?
Your given Arr-Stack seems to me relative complex when you are a beginner with podman.
Probably you could get some experience, when you start with just a single container.
In following posts are my personal quadlet settings for running Portainer, which could be helpful for getting insights of your running containers.
https://docs.portainer.io/start/install-ce/server/podman/linux
[Install]
\# Start by default on boot without explicit enabling
\# To avoid automatic start Install section has to be
\# disabled
WantedBy=default.target multi-user.target
[Service]
\# Restart service in case of failures
Restart=on-failure
TimeoutStartSec=20
TimeoutStopSec=20
Type=notify
[Unit]
Description=Container running Portainer container management platform
Wants=podman-user-wait-network-online.service
After=podman-user-wait-network-online.service
After=local-fs.target
Requires=podman.socket
@Excaliburr 3. Are we talking here about rootless podman? If yes, containers are running on the host with the uid of current user, in your example with UID 1000.
Processes IN started containers are often running with UID=0, but this belongs to definition of used container and is only IN container.
PostgreSQL in Debian container is running with UID=999.
To avoid problems with created files in host file system, I’m using UserNS=keep-id:uid=999,gid=999, which maps files to the UID on host system.
@Nighed Sorry, but I currently don’t use Opencloud and I don’t have insights in the code.
But maybe the code itself has an answer for your question.
https://github.com/opencloud-eu
@mjr I think, you are writing about Owncloud.
Opencloud is newly written with Go, so it can’t be a fork of PHP driven Owncloud or Nextcloud.
Probably https://opencloud.eu/ could be an alternative.
@theorangeninja I would suggest again, that you try to access the content of the podman volume as host user, which is running the podman container.
I think, that it would looks like this and that you can only access it using podman unshare:
drwxr-xr-x 1 166446 166446 66 28. Jul 20:43 \_data
@theorangeninja Did you have tried a ls -al on the used volume?
The podman volume path can be found here:
`podman info --format ‘{{.Store.VolumePath}}’``
When you use $HOME/linkding as volume mount and the linkding container process is running with <> UID 0, then the created files are belonging to another UID than your UID.
Maybe this tutorial explains it better:
https://www.tutorialworks.com/podman-rootless-volumes/
@theorangeninja Rootless podman container and owner of created files - always a mystery.
Maybe, the part belonging to “Using volumes” could help:
https://github.com/containers/podman/blob/main/docs/tutorials/rootless/_tutorial.md
If the container process is running with another UID than 0 (root), created files on the host belongs to another UID, calculated based on settings from /etc/suduid.
You should have a look into --userns for mapping of UIDs between container and host:
https://docs.podman.io/en/latest/markdown/podman-run.1.html
For PostgreSQL I’m using keep-id:uid=999,gid=999.
@Cenzorrll For comparison of LVM with BTRFS there are several article available.
https://www.baeldung.com/linux/btrfs-lvm
https://fedoramagazine.org/choose-between-btrfs-and-lvm-ext4/
From personal experience, I have an encrypted software RAID1 with mdadm and BTRFS on top.
Is not LVM, but same direction.
Before implementing this, I made some tests.
Related to encryption, when RAID1 was implemented with BTRFS, the CPU load had been doubled, because every BTRFS disk has an encryption process.
With software RAID1, only one encryption process is there.
@irmadlad You are welcome.
The Arch Wiki also has a lot information about Power Management.
And I would say, most of them are independent if Arch Linux is used or not.
@irmadlad That have also been my intentions, when I created the udev rules.
They are most generic and I use them on several systems for reducing some small power consumption.
Example: enabling of PCI power management
ACTION=="add|change", \\
SUBSYSTEM=="pci", \\
ATTR{power/control}="auto"
The things, which you listed in your first post are from my view good topics, for getting maximum results from minimum effort.
I started at
https://wiki.archlinux.org/title/powertop
and went further from there.
@FilthyShrooms From my point of view most Linux- or *BSD-OS will be a good choice.
I’m running rootless podman on Manjaro Linux, but for many people an Arch Linux based system can be problematic related to possible stability issues from rolling updates.
A Debian based distribution could be a better choice for many people, especially when the provided services are running as container or in another virtualized environment.