thank you rimelek
i want to solve next web access inconsistnce (with and without docker - wordpress vs phpmyadmin) so i will have the same web access ibehavior without and with docker
wordpress + phpmyadmin
: without docker : works well - as expected
: with docker : wordpress behave the same (nice) - phpmyadmin does not (need YAML port postfix, revproxi cfg, which multiplies with multiple instances)
BTW i tested your suggestion sooner with same EXIT code 1 (error) and the error comes from first 80 (eg - 127.1.0.1:80:80) so I am curious when Iooking at screenshot ebove docker ps that phpmyadmin service …wp1-phpmyadmin-1 || -2 must have different ports e.g. 8080, 8091 + rev proxi cfg and special access with docker … but …wp1-wordpress-1 || -2 have identical (9000/tcp) and same access with and without docker (it means that HTTP(S) service connect over the port 9000 and goes to wp1 || wp2 when I call https:// mywp1.tld || https:// mywp2.tld). This means that synology make it systematic - the way how I want to get with phpmyadmin via docker should be also systematic - the way with phpmyadmin now is not really usefull.
Note to solve the docker incosistsnce behavior with and without docker synology suggested is to use ports in YAML cfg like I did so far e.g. 8080:80 or 8091:80 + reverse proxi - but they also said I need to ask docker specialist for simpler way / consitent way to overpass this workaround from synology … which I do