Increase debug logging for CloudQuery plugin containers in Docker

Is there any way to increase debug logging for running plugins via Docker containers? I have CQ starting the plugin container, but it never communicates with it successfully. I can’t figure out why, as all networking looks fine.

@relieved-teal Could you share your CloudQuery config with any sensitive values removed? And can you describe your setup in a bit more detail?

There is no way to increase debug logging for Docker containers specifically, but you can try using

--log-level debug

when running the CLI or plugin.

I think my setup is just unsupported: I’m trying to run the CLI in a container with the Docker socket mapped as a volume. CQ seems to start a container and map a random host port to 7777 then connect to it on localhost (although it has it bind to 0.0.0.0 seemingly). This, of course, doesn’t work in a container.

Would be great to support this. Maybe it could start the plugin container on the same network as the CLI’s via some introspection and talk to it over Docker networking instead of via host bound port.