tidy: formatting

This commit is contained in:
redbeardymcgee 2024-12-03 14:00:50 -06:00
parent 80f392476d
commit f3fca31dd9
2 changed files with 27 additions and 18 deletions

View file

@ -3,7 +3,8 @@
My proof of concept server running this container stack is built on AlmaLinux My proof of concept server running this container stack is built on AlmaLinux
9.4. 9.4.
> [!WARNING] Perform `dnf update` immediately > [!WARNING]
> Perform `dnf update` immediately
### [Repositories](https://wiki.almalinux.org/repos/) ### [Repositories](https://wiki.almalinux.org/repos/)
@ -103,15 +104,16 @@ printf '%s\n' \
## Cockpit -> https://ip-addr:9090 ## Cockpit -> https://ip-addr:9090
> [!WARNING] Disable the firewall if you are lazy > [!WARNING]
> Exposing ports for other services can be exhausting and I have not learned > Disable the firewall if you are lazy Exposing ports for other services can be
> how to do this for containers properly. Each container may need a new rule > exhausting and I have not learned how to do this for containers properly.
> for something, not sure. > Each container may need a new rule for something, not sure.
> ```bash > ```bash
> systemctl disable --now firewalld > systemctl disable --now firewalld
> ``` > ```
> [!TODO] Should be able to set up good firewall with only 80/443 open. > [!NOTE]
> Should be able to set up good firewall with only 80/443 open.
Enable the socket-activated cockpit service and allow it through the firewall. Enable the socket-activated cockpit service and allow it through the firewall.
@ -125,7 +127,8 @@ firewall-cmd --reload
### Add SSH keys ### Add SSH keys
> [!TIP] Skip if you copied your keys with `ssh-copy-id` above. > [!TIP]
> Skip if you copied your keys with `ssh-copy-id` above.
`Accounts` -> `Your account` -> `Authorized public SSH keys` -> `Add Key` `Accounts` -> `Your account` -> `Authorized public SSH keys` -> `Add Key`
@ -149,14 +152,15 @@ dnf install podman
systemctl enable --now podman systemctl enable --now podman
``` ```
> [!NOTE] Read the docs. > [!NOTE]
> Read the docs.
> `man podman-systemd.unit` > `man podman-systemd.unit`
### Prepare host networking stack ### Prepare host networking stack
#### slirp4netns #### slirp4netns
> [!TODO] > [!NOTE]
> This may not be necessary but my system is currently using it. > This may not be necessary but my system is currently using it.
```bash ```bash
@ -165,16 +169,18 @@ dnf install slirp4netns
#### Install DNS server for `podman` #### Install DNS server for `podman`
> [!TODO] > [!NOTE]
> Not sure how to resolve these correctly yet but the journal logs it > Not sure how to resolve these correctly yet but the journal logs it
> so it's running for something. > so it's running for something.
```bash ```bash
dnf install aardvark-dns dnf install aardvark-dns
``` ```
#### Allow rootless binding port 80+ #### Allow rootless binding port 80+
> [!NOTE] This is only necessary if you are setting up the reverse proxy. > [!NOTE]
> This is only necessary if you are setting up the reverse proxy.
```bash ```bash
printf '%s\n' 'net.ipv4.ip_unprivileged_port_start=80' > /etc/sysctl.d/99-unprivileged-port-binding.conf printf '%s\n' 'net.ipv4.ip_unprivileged_port_start=80' > /etc/sysctl.d/99-unprivileged-port-binding.conf
@ -214,11 +220,12 @@ usermod --add-subuids 200000-299999 --add-subgids 200000-299999 $ctuser
loginctl enable-linger $ctuser loginctl enable-linger $ctuser
``` ```
> [!TIP] Optionally setup ssh keys to directly login to $ctuser. > [!TIP]
> Optionally setup ssh keys to directly login to $ctuser.
> [!NOTE] The login shell doesn't exist. > [!NOTE]
> Launch `bash -l` manually to get a shell or else your `ssh` will exit with a > The login shell doesn't exist. Launch `bash -l` manually to get a shell or
> status of 1. > else your `ssh` will exit with a status of 1.
### Setup $ctuser env ### Setup $ctuser env
@ -236,10 +243,12 @@ systemctl --user enable --now podman-auto-update
exit exit
``` ```
> [!WARNING] I disabled SELinux to not deal with this for every container. > [!WARNING]
> I disabled SELinux to not deal with this for every container.
> /etc/selinux/config -> `SELINUX=disabled` > /etc/selinux/config -> `SELINUX=disabled`
> [!TODO] Set up the correct policies permanently instead of disabling SELinux > [!NOTE]
> Set up the correct policies permanently instead of disabling SELinux
Temporarily set SELinux policy to allow containers to use devices. Temporarily set SELinux policy to allow containers to use devices.

View file

@ -102,7 +102,7 @@ Dec 01 08:42:05 perseus helloworld[1143334]: Mastodon: @Podman_io@fosstodon.org
```bash ```bash
# Step 1 # Step 1
git clone --depth=1 https://github.com/redbeardymcgee/podbox git clone --depth=1 https://github.com/redbeardymcgee/podbox
cp -a "podbox/quadlets/thelounge" "$XDG_CONFIG_HOME/containers/systemd/" cp -a podbox/quadlets/thelounge "$XDG_CONFIG_HOME"/containers/systemd/
# Step 2 # Step 2
$EDITOR "$XDG_CONFIG_HOME"/containers/systemd/thelounge/* $EDITOR "$XDG_CONFIG_HOME"/containers/systemd/thelounge/*
# Step 3 # Step 3