Replies: 3 comments 1 reply
|
My post just deleted itself - for now you can view the previous version by clicking on "edited" in the top right corner. I'm going to try and figure out what is going on and revert it if possible. |
0 replies
|
I extracted the markdown from the previous version of the post, so here it is: Edit by @imnotjames: Moved to top post |
0 replies
|
It looks like you've turned on the firewall with nixos - perhaps some default rules are causing blocking? I ran the same compose yaml and couldn't reproduce. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
What went wrong?
Hello!
I've run into a host resolution issue when migrating Grimmory from one host to another. I was able to work around this issue by manually setting the mariadb IP address on every restart, but this is not ideal. Here is what happened:
I installed Grimmory around a month ago on a debian machine via docker-compose, and it worked fine. I am just now setting up Proxmox, and one of the first things I did was create a VM for Grimmory. Then, my process went like this:
docker compose pull). After this it still works.podmananddocker-composeon the media VM.docker compose upMy docker-compose.yml file initially did not specify networks, and so I thought the issue might be with the switch between Podman and Docker's networks, but adding networks manually did not fix the issue.
Here are some of the things I've tried:
docker-composetopodman-compose--> Same issuemariadbhostname from another container in the same network --> Name resolution failsmariadbcontainer --> It works, but isn't stable across restarts.How can we reproduce it?
I've provided the NixOS configuration and Docker compose file.
What Build of Grimmory are you on?
Stable
Your setup
Machine A (Debian)
Machine B (NixOS VM)
Nix System files
Grimmory and docker-compose
Screenshots or error messages (optional)
Stack Trace
Stack Trace
docker compose ps output
This is what shows up if I run docker compose ps while it is running.
Trying to lookup mariadb in the network
Finding mariadb IP directly
Name resolution isn't working, but I can connect to the mariadb container's IP directly.
I can use this to get Grimmory up and running, but I have to change the MariaDB IP address every time I restart. The general process for doing this looks like this:
All reactions