#systemdnspawn — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #systemdnspawn, aggregated by home.social.
-
Почему Docker не всегда лучший выбор и чем его заменить
Docker — отличный инструмент, но «отличный» не значит «единственный» и тем более не значит, что он подходит для любой задачи. На одиночном сервере с одним-двумя приложениями Docker может принести больше проблем, чем пользы. Демон, образы, слои, сети и тома упрощают упаковку и запуск приложений, но на одиночке или небольшом VDS они избыточны. Под катом о том, в каких случаях Docker не нужОн, чем его заменить и как. Читать
https://habr.com/ru/companies/ruvds/articles/1060030/
#Docker #Podman #systemd #systemdnspawn #Incus #Firejail #Linuxконтейнеры #контейнеризация #администрирование_серверов #ruvds_статьи
-
While updating my systemd nspawn container server at home:
```
666 packages can be upgraded. Run 'apt list --upgradable' to see them.
```
🎶 6 -- 6 -- 6 -- the number of the packages 🎶What could possibly go wrong. 🤷♂️
-
While updating my systemd nspawn container server at home:
```
666 packages can be upgraded. Run 'apt list --upgradable' to see them.
```
🎶 6 -- 6 -- 6 -- the number of the packages 🎶What could possibly go wrong. 🤷♂️
-
systemd-nspawn: продолжаем знакомство
Привет, это снова Егор Гаврилов. И я сегодня и дальше познакомлю аудиторию с systemd-nspawn. Это продолжение предыдущей моей статьи про systemd-nspawn .
-
systemd-nspawn: запускаем FidoIP на Arch Linux
Привет, это снова Егор Гаврилов. Сегодня расскажу про то, как настроить FidoIP на Arch Linux, используя инструмент, входящий в состав systemd , под названием systemd-nspawn .
https://habr.com/ru/articles/962368/
#systemd #systemdnspawn #fidoip #fidoip_204 #fidonet #фидонет #фидо
-
The container knows of two `/tmp` mounts now. The latter is mounted over the first one. I'd prefer if I could change the size of the first one.
```
root@jellyfin:~# mount | grep /tmp
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,size=1622240k,nr_inodes=409600,uid=1660485632,gid=1660485632,inode64)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,size=2097152k,uid=1660485632,gid=1660485632,inode64)
``` -
The container knows of two `/tmp` mounts now. The latter is mounted over the first one. I'd prefer if I could change the size of the first one.
```
root@jellyfin:~# mount | grep /tmp
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,size=1622240k,nr_inodes=409600,uid=1660485632,gid=1660485632,inode64)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,size=2097152k,uid=1660485632,gid=1660485632,inode64)
``` -
The upgrade to Jellyfin 10.11.0 requires a `/tmp/` of at least 2G. My systemd-nspawn container only provided 1.6G. To resize it I added `TemporaryFileSystem=/tmp:nosuid,size=2G` under the `[Files]` section in its `.nspawn` file. After a restart Jellyfin started its migrations.
I'm not sure if this is the correct way but it works and I can roll back the change after the upgrade.
-
The upgrade to Jellyfin 10.11.0 requires a `/tmp/` of at least 2G. My systemd-nspawn container only provided 1.6G. To resize it I added `TemporaryFileSystem=/tmp:nosuid,size=2G` under the `[Files]` section in its `.nspawn` file. After a restart Jellyfin started its migrations.
I'm not sure if this is the correct way but it works and I can roll back the change after the upgrade.
-
The thing I hate about #Discourse is the need to use docker. Docker is a PITA to run in systemd-nspawn, and I guess #lxc, too. I would put much more energy into hosting my Discourse if I just could install it in my system containers without too much hassle.
Other than that, Discourse is great.
-
The thing I hate about #Discourse is the need to use docker. Docker is a PITA to run in systemd-nspawn, and I guess #lxc, too. I would put much more energy into hosting my Discourse if I just could install it in my system containers without too much hassle.
Other than that, Discourse is great.
-
Did anyone try to use #systemd nspawn as OCI runtime with #kubernetes ? Is there some usable guide how to set this easily to try out? #k8s #systemdnspawn
-
Did anyone try to use #systemd nspawn as OCI runtime with #kubernetes ? Is there some usable guide how to set this easily to try out? #k8s #systemdnspawn