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
Hi,
I rebuild my images today and after that it seems like seahub isn't coming up.
(I build the images myself, with this repo here and don't use the docker hub images.)
Caddy gets timeout requesting 172.25.0.6:8000 and 172.25.0.5:8082. So seahub and seafhttp? are not up.
The only curios thing I can really see in the logs is: seahub_1 | Error happened during creating seafile admin.
Perhaps some Python dependency got updated and broke something?
Can someone confirm the same behavior?
The text was updated successfully, but these errors were encountered:
I found my problem. I ran into an Docker+firewalld Bug which broke internal network communication between docker containers. (moby/libnetwork#2647).
I have no idea why this showed today, I use this setup since a long time. Perhaps it emerged with an docker-ce update this week.
Hi,
I rebuild my images today and after that it seems like seahub isn't coming up.
(I build the images myself, with this repo here and don't use the docker hub images.)
Caddy gets timeout requesting 172.25.0.6:8000 and 172.25.0.5:8082. So seahub and seafhttp? are not up.
The only curios thing I can really see in the logs is: seahub_1 | Error happened during creating seafile admin.
Perhaps some Python dependency got updated and broke something?
Can someone confirm the same behavior?
The text was updated successfully, but these errors were encountered: