Review WildFly service status check in Docker deployments

Background

The current code skips the service wildfly status command for Docker deployments:

if [[ "$DEPLOYMENT_TYPE" == "Docker" ]]; then
echo "Running inside Wildfly container" >> "$LOGFOLDER/services.txt"
else
service wildfly status >> "$LOGFOLDER/services.txt" || true
fi

It should be investigated whether this distinction is actually necessary and what service wildfly status does on the supported deployments.

The service uses:

ExecStart=/opt/wildfly/bin/launch.sh ...

The service wildfly status command may therefore ultimately execute launch.sh, which could use the JBoss/WildFly CLI to retrieve the application server status.

Task

Investigate whether service wildfly status can safely be executed in Docker deployments as well.

Determine:

What service wildfly status actually executes on Debian.
Whether it ultimately invokes launch.sh and/or the WildFly/JBoss CLI.
Whether the command behaves differently inside a WildFly Docker container.
Whether skipping the command for Docker is necessary.
Whether a deployment-independent WildFly status check would be preferable.