localhost name resolution about tasmobackupv1

[lynema]

The same issue occurred using podman on both Fedora Core OS and Fedora SilverBlue.

wait-for-it.sh: waiting 45 seconds for localhost:9000
[23-Aug-2020 03:28:45] NOTICE: fpm is running, pid 15
[23-Aug-2020 03:28:45] NOTICE: ready to handle connections
2020-08-23 03:28:46,947 INFO success: processes entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-08-23 03:28:46,948 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-08-23 03:28:48,954 INFO success: php-fpm entered RUNNING state, process has stayed up for > than 3 seconds (startsecs)
wait-for-it.sh: timeout occurred after waiting 45 seconds for localhost:9000

Port 9000 is listening

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 localhost:9000 0.0.0.0:* LISTEN

[lynema]

Copying a hosts file with just the IPv4 items and running
podman create --no-hosts=true -p 8259:80 -v /root/tasmobackupdata:/var/www/html/data:z -e DBTYPE=sqlite -e DBNAME=data/tasmobackup --name TasmoBackup danmed/tasmobackupv1
to create the container worked.

[patrickdk77]

This should be all corrected in 1.03.20

[patrickdk77]

I have redone this support again, as my previous fix was to change everything to 127.0.0.1, but I think I remember someone running ipv6 only containers had an issue with that. So I switched everything to use localhost, and did a solution much like lynema did. I test ipv4 and ipv6 localhost, and disable one if it isn't working. I've stood up some ipv6 containers to test on and my testing looks ok. But if anyone wants to test I can point you ad an image: docker pull patrickdk/tasmobackupv1:1.04.12