TL;DR - Were there any recent changes to Fly’s infrastructure that could break an app’s ability to detect if it’s running in a container?
The long version
I’ve been running FusionAuth via a Docker image on Fly for a couple months and things have been relatively smooth sailing. In the last day or two the app suddenly stopped working though. My ability to debug is hindered because FusionAuth is closed-source and logging very little, but according to the one error I’m getting back the issue appears to be that FusionAuth recently started trying write log files:
/usr/local/fusionauth/fusionauth-app/apache-tomcat/bin/catalina.sh: line 401: /usr/local/fusionauth/fusionauth-app/apache-tomcat/../../logs/fusionauth-app.log: Permission denied
FusionAuth is supposed to write to STDOUT instead of that log file when run in a container (see Monitoring FusionAuth). This behavior worked until very recently. I’ve already reached out to the FusionAuth team, but given that the exact same FusionAuth docker image was chugging along just fine and now refuses to start I’m wondering if something could have changed with Fly.
Any help is appreciated!