Docker container is running a standard Ubuntu 16.04 LTS distribution, not a shared hosting, a PaaS platform, Windows, a NAS box. Sadly, it’s not the environment that is broken, but rather tt-rss itself.
By the way, by jumping to such unreasonable conclusions, you’re
a) ignoring bugs in YOUR code from honest users reporting bugs
b) encouraging users reporting bugs to lie about the environment
it doesn’t matter. i don’t provide dockerfiles which means whatever you’re running is unsupported and i’m not going to debug your configuration for you.
of course, it’s entirely possible. if you manage to identify the issue and it is within tt-rss code i’ll be glad to accept your pull request with the fix.
unsupported doesn’t mean you won’t get any help here, try to rethink your approach to posting though. there’s no need to be upset.
i’ll also mention third party dockerfiles in the rules, just so that would be more clear.
e: the particular issue with docker is that it’s easy to screw up something if you’re using a forward proxy and don’t know what you’re doing which could lead to all sorts of crazy issues i’m not really interested in investigating.