Open Juliasmatius opened 3 days ago
Can you try to remove PEERTUBE_REDIS_*
variables from your env file?
Sure!
The log for that is https://pastebin.com/8kGbr7RF
Can you go inside your peertube
container and try to ping redis
? (ping
is not in the peertube container but you can try curl -v redis:6379
)
I seem to be getting a response.
root@v25159:~/docker/peertube# docker exec -it peertube-peertube-1 bash
root@df89efbf35b3:/app# curl -v redis:6379
* Trying [2001:db8:2::2]:6379...
* Connected to redis (2001:db8:2::2) port 6379 (#0)
> GET / HTTP/1.1
> Host: redis:6379
> User-Agent: curl/7.88.1
> Accept: */*
>
* Empty reply from server
* Closing connection 0
curl: (52) Empty reply from server
Hope this solves it: https://github.com/Chocobozzz/PeerTube/commit/f4339cfb72ac80c1c68059496da99797c4a0484b
The IPv6 2001:db8:-Range is for documentation only.
That change requires line 52 of the compose file to be changed to the container stairs up. I set it to ipv6_address: fdab:e4b3:21a2:ef1b:0000:0000:0000:0123
for testing. But i still get the same error. log
I am also not a 100% sure i modified the compose file correctly so thats here https://pastebin.com/J3wR0CPW
Describe the problem
When trying to launch the peertube docker container i get the following crash
https://pastebin.com/xDS3VvGB
I've tried to define redis instance information in .env
and here's the compose file.
Additional information