Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vod2pod cannot connect to redis on podman #179

Open
2 tasks
lukaslcf opened this issue Jun 8, 2024 · 6 comments
Open
2 tasks

vod2pod cannot connect to redis on podman #179

lukaslcf opened this issue Jun 8, 2024 · 6 comments

Comments

@lukaslcf
Copy link

lukaslcf commented Jun 8, 2024

app version: 1.2.1

  • twitch api key set
  • youtube api key set

issue description:

The vod2pod cannot connect to the Redis server started using the same docker compose script. The only thing I changed in the docker-compose.yml is the host port to 9001.

I use podman-compose up to start the containers.

Log:

podman start -a vod2pod-rss_redis_1                                                                                   │
1:C 08 Jun 2024 20:03:47.462 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo                                          │
1:C 08 Jun 2024 20:03:47.462 # Redis version=6.2.14, bits=64, commit=00000000, modified=0, pid=1, just started        │
1:C 08 Jun 2024 20:03:47.462 # Configuration loaded                                                                   │
1:M 08 Jun 2024 20:03:47.462 # Server initialized                                                                     │
1:M 08 Jun 2024 20:03:47.462 # WARNING Memory overcommit must be enabled! Without it, a background save or replication│
 may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see│
 https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.con│
f and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.                         │
podman start -a vod2pod-rss_vod2pod_1                                                                                 │
2024-06-08T20:03:48.491Z INFO  [app] app version 1.2.1                                                                │
thread 'main' panicked at src/main.rs:22:9:                                                                           │
Error interacting with Redis (redis is required): failed to lookup address information: No address associated with hos│
tname                                                                                                                 │
                                                                                                                      │
Location:                                                                                                             │
    /tmp/vod2pod/src/lib.rs:13:15                                                                                     │
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace                                         │
exit code: 101       
@madiele
Copy link
Owner

madiele commented Jun 10, 2024

The problem seems to be that podman does not populate the internal dns with "redis", did you change the name of the redis container inside the compose?

@madiele
Copy link
Owner

madiele commented Jun 10, 2024

You could also play around with the hostname field to see if it helps

@madiele
Copy link
Owner

madiele commented Jun 10, 2024

Based on this stackoverflow answers you might also be missing the dns plugin for podman

https://stackoverflow.com/questions/66895304/unable-to-resolve-hostname-with-docker-compose-and-podman

Give it a check

@lukaslcf
Copy link
Author

lukaslcf commented Jun 10, 2024

Thanks a lot for coming back to this issue. I will take a look later today to see if the missing plug-in is the problem.

The compose config is not changed from the one provided in the repo.

@lukaslcf
Copy link
Author

I checked my setup, indeed the dnsname plugin was missing for cni. I would also need to enable the plugin for the existing network configs.

However, it was suggested to move to netavark for future podman networking, so I will try that instead (plus the aardvark-dns plugin)

@madiele
Copy link
Owner

madiele commented Jun 10, 2024

Ok feel free to close the issue when you tested that it works ✌️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants