No automation logs in docker logs output

[BrGitHub11]

I installed ManageIQ using the docker method mentioned here:
https://www.manageiq.org/docs/get-started/docker

I attached ManageIQ to our VMware instance and to our Ansible Tower server.
Then I created a service dialog and a service item.
I'm able to deploy VMs from the service ui. I could see log output under Services Requests, Request Logs.
But nothing in the docker logs output.

My questions:

1. how could I enable automation log output to docker logs
2. how could I enable debug output for automation tasks

[kbrock]

related to ManageIQ/manageiq-content#730

[Fryguy]

As commented in ManageIQ/manageiq-content#730 (comment)

@BrGitHub11 In containerized deployments the logs get written to stdout and are not written to disk (journalctl doesn't exist in containers). That page should be hidden in containerized deployments, so if that's showing that's a bug. You should enable a log aggregator such as an EFK stack if running in a containerized deployment.

[Fryguy]

All logs should be written to STDOUT, so if they are not all there that is probably a bug.

[BrGitHub11]

Hi Jason,
I'm looking at the docker logs output which should capture the STDOUT of the container. I could see other outputs of ManageIQ but no automation log output.

[Fryguy]

Sounds like an issue with logging + a check for whether it's kube vs docker vs appliance.

[BrGitHub11]

Were you able to reproduce the issue?

[miq-bot]

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation.

[miq-bot]

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

[miq-bot]

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

[miq-bot]

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

[miq-bot]

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

[miq-bot]

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.