You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to setup nextcloud-aio for two users. userA and userB, each having a linux user with a quadlet file.
I'm on Rocky Linux and I tested on podman 5.2.2 and I also installed Podman 5.3.1 because I heard container<>host was easier with 5.3.x.
For this example, let's call my domain usera.domain.local.
Caddy is installed natively, and I can connect to nextcloud but Onlyoffice doesn't work. It requires a loopback / calling the host it's installed on. ie https://usera.domain.local from within the container.
I don't have the errors I had with 5.2.2 on hand, so let's focus on the latest and greatest :) I must say, after updating to 5.3.1 (I used the CentOS rpm, no issue installing), I did some testing (see below) then I thought I should delete and recreate everything - but now there is no internet connection inside the container it would seem, I cannot ping or anything and nextcloud apps won't install.
The officiel nextcloud AIO readme file state that podman isn't supported, but it appear that many was succesful. I have no clue why this isn't working in my case.
I'm asking here because I know this is the best community to help me figure this out.
Quadlet
[Container]
ContainerName=nextcloud-aio-mastercontainer
Environment=NEXTCLOUD_DATADIR=/mnt/data/nextcloud/testa.domain.local
Environment=APACHE_PORT=10001
Environment=TALK_PORT=10002
Environment=APACHE_IP_BINDING=0.0.0.0
Environment=WATCHTOWER_DOCKER_SOCKET_PATH=/run/user/1002/podman/podman.sock
Environment=SKIP_DOMAIN_VALIDATION=True
Image=docker.io/nextcloud/all-in-one:latest
Network=bridge
PublishPort=127.0.0.1:10003:8080
Volume=/run/user/1002/podman/podman.sock:/var/run/docker.sock:ro,z
Volume=nextcloud_aio_mastercontainer:/mnt/docker-aio-config
PodmanArgs=--security-opt label:disable
AutoUpdate=registry
Pull=newer
AddHost=testa.domain.local:host-gateway # < that was for testing stuff
[Unit]
Description=NextCloud for usera at testa.domain.local
Documentation=https://github.com/nextcloud/all-in-one/blob/main/docker-rootless.md
After=local-fs.target
Requires=podman.socket
After=podman-user-wait-network-online.service
[Install]
WantedBy=multi-user.target default.target
Before install Podman 5.3.1, I was on 5.2.2 and from inside the host I could ping the domain, but curl -I usera.domain.local wouldn't work. Now, both ping and curl doesnt work on 5.3.1, I get bad host.
nslookup is now similar:
# nslookup usera.domain.test
;; communications error to 10.89.0.1#53: timed out
;; communications error to 10.89.0.1#53: timed out
With 5.3.1, before reinstalling
In Nextcloud I get:
Error when trying to connect (cURL error 7: Failed to connect to usera.domain.local port 443 after 10002 ms: Could not connect to server (see https://curl.haxx.se/libcurl/c/libcurl-errors.html)
When I try to add host-gateway:
Dec 13 22:45:28 nextcloud[179628]: Error: failed to create new hosts file: unable to replace "host-gateway" of host entry "usera.domain.local:host-gateway": host containers internal IP address is empty
With containers/containers.conf as suggested here (But I removed host-gateway) :
Stopping and restarting the service systemctl --user restart nextcloud.service:
Dec 13 22:39:36 podman[179543]: 2024-12-13 22:39:35.97063503 +0000 UTC m=+0.468367594 image pull e9ce9a27aefa1e3b86176b55d4e694c65076300615573c220d93f3168faa5334 docker.io/nextcloud/all-in-one:latest
Dec 13 22:39:36 podman[179543]: 2024-12-13 22:39:36.027197711 +0000 UTC m=+0.524930245 container create 83c43e73ee034046d7aadd4ec8adc597e9fd3a5207b5f36dbd41782cc29c9de2 (image=docker.io/nextcloud/all-in-one:latest, name=nextcloud-aio-mastercontainer, io.containers.auto>
Dec 13 22:39:36 pasta[179566]: Couldn't set IPv6 route(s) in guest: No route to host
Dec 13 22:39:36 podman[179543]: 2024-12-13 22:39:36.123350445 +0000 UTC m=+0.621082989 container remove 83c43e73ee034046d7aadd4ec8adc597e9fd3a5207b5f36dbd41782cc29c9de2 (image=docker.io/nextcloud/all-in-one:latest, name=nextcloud-aio-mastercontainer, PODMAN_SYSTEMD_UNI>
Dec 13 22:39:36 nextcloud[179543]: Error: setting up Pasta: pasta failed with exit code 1:
Dec 13 22:39:36 nextcloud[179543]: Couldn't set IPv6 route(s) in guest: No route to host
I tried adding the domains to /etc/hosts as some suggested, but no luck.
System
# uname -a
Linux test 5.14.0-503.15.1.el9_5.x86_64 #1 SMP PREEMPT_DYNAMIC Tue Nov 26 17:24:29 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
Firewall
# firewall-cmd --list-all
public (active)
target: default
icmp-block-inversion: no
interfaces: eno1
sources:
services: cockpit dhcpv6-client https ssh
ports: 443/tcp 80/tcp
protocols:
forward: yes
masquerade: no
forward-ports:
source-ports:
icmp-blocks:
rich rules:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm trying to setup nextcloud-aio for two users. userA and userB, each having a linux user with a quadlet file.
I'm on Rocky Linux and I tested on podman 5.2.2 and I also installed Podman 5.3.1 because I heard container<>host was easier with 5.3.x.
For this example, let's call my domain usera.domain.local.
Caddy is installed natively, and I can connect to nextcloud but Onlyoffice doesn't work. It requires a loopback / calling the host it's installed on. ie https://usera.domain.local from within the container.
I don't have the errors I had with 5.2.2 on hand, so let's focus on the latest and greatest :) I must say, after updating to 5.3.1 (I used the CentOS rpm, no issue installing), I did some testing (see below) then I thought I should delete and recreate everything - but now there is no internet connection inside the container it would seem, I cannot ping or anything and nextcloud apps won't install.
The officiel nextcloud AIO readme file state that podman isn't supported, but it appear that many was succesful. I have no clue why this isn't working in my case.
I'm asking here because I know this is the best community to help me figure this out.
Quadlet
Before install Podman 5.3.1, I was on 5.2.2 and from inside the host I could ping the domain, but
curl -I usera.domain.local
wouldn't work. Now, both ping and curl doesnt work on 5.3.1, I getbad host
.nslookup is now similar:
With 5.3.1, before reinstalling
In Nextcloud I get:
When I try to add
host-gateway
:With
containers/containers.conf
as suggested here (But I removed host-gateway) :Stopping and restarting the service
systemctl --user restart nextcloud.service
:I tried adding the domains to
/etc/hosts
as some suggested, but no luck.System
Firewall
Inspect
Beta Was this translation helpful? Give feedback.
All reactions