Fix podman hostnames
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:
parent
bd7e4a3193
commit
b6f39969cc
|
@ -27,7 +27,7 @@ http {
|
|||
#gzip on;
|
||||
|
||||
upstream php-handler {
|
||||
server nextcloud-nextcloud:9000;
|
||||
server localhost:9000;
|
||||
}
|
||||
|
||||
server {
|
||||
|
|
|
@ -24,7 +24,7 @@
|
|||
|
||||
environment = {
|
||||
DB_TYPE = "postgres";
|
||||
DB_HOST = "gitea-postgres:5432";
|
||||
DB_HOST = "localhost:5432";
|
||||
DB_NAME = "gitea";
|
||||
DB_USER = "gitea";
|
||||
|
||||
|
|
|
@ -19,7 +19,7 @@
|
|||
environment = {
|
||||
POSTGRES_DB = "nextcloud";
|
||||
POSTGRES_USER = "nextcloud";
|
||||
POSTGRES_HOST = "nextcloud-postgres";
|
||||
POSTGRES_HOST = "localhost";
|
||||
OVERWRITEPROTOCOL = "https";
|
||||
TRUSTED_PROXIES = "127.0.0.1";
|
||||
};
|
||||
|
|
Loading…
Reference in a new issue