tlaternet/tlaternet-server
1
0
Fork 0
Code Issues 9 Pull requests Releases Activity

Fix podman hostnames

Browse source 
It seems that with the newest version of podman container names are no
longer added as hostnames, meaning that any attempt to resolve
hostnames with the current config will fail. `localhost` is probably
more robust anyway, so we switch to that.

The bug manifests as broken services because nextcloud/gitea cannot
resolve their databases and nextcloud fails to resolve the php
server. To fix this a running system, the gitea and nextcloud database
configurations will need to be hand-edited, since those values are
only set on initialization, and not updated when changed later.
This commit is contained in:
Tristan Daniël Maat 2022-01-08 00:27:01 +00:00
parent bd7e4a3193
commit b6f39969cc
Signed by: tlater
GPG key ID: 49670FD774E43268
3 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
configuration/services/configs/nginx-nextcloud.conf
View file

@ -27,7 +27,7 @@ http {
#gzip on; #gzip on;
upstream php-handler { upstream php-handler {
server nextcloud-nextcloud:9000; server localhost:9000;
} }
server { server {

2
configuration/services/gitea.nix
View file

@ -24,7 +24,7 @@
environment = { environment = {
DB_TYPE = "postgres"; DB_TYPE = "postgres";
DB_HOST = "gitea-postgres:5432"; DB_HOST = "localhost:5432";
DB_NAME = "gitea"; DB_NAME = "gitea";
DB_USER = "gitea"; DB_USER = "gitea";

2
configuration/services/nextcloud.nix
View file

@ -19,7 +19,7 @@
environment = { environment = {
POSTGRES_DB = "nextcloud"; POSTGRES_DB = "nextcloud";
POSTGRES_USER = "nextcloud"; POSTGRES_USER = "nextcloud";
POSTGRES_HOST = "nextcloud-postgres"; POSTGRES_HOST = "localhost";
OVERWRITEPROTOCOL = "https"; OVERWRITEPROTOCOL = "https";
TRUSTED_PROXIES = "127.0.0.1"; TRUSTED_PROXIES = "127.0.0.1";
}; };