Make it easier to deploy lazydocker as part of a container 'stack'

My need: include a tool to allow the end users to 'monitor this set of containers', as part of an application which is deployed as a set of containers managed via docker-compose

Ideally, I would be running lazydocker as one more container within the 'app' stack.
- no need for lazydocker to 'display' or 'manage' other services/containers/images present on the host, apart from the ones related to the current app
- no need for lazydocker to create containers / modify containers config

So far I have included Portainer as a "self-contained container monitor" solution along with my application stacks, but it seems to
- include too many features that do not apply to my case ('manage' vs. 'monitor')
- not be tailored to monitor a single set of containers running on localhost, as much as monitoring different hosts, and on each manage all container resources

So far I managed to achieve a good part of what I need by:
- adding to my stack a container that can run lazydocker (and `docker`)
- mounting into it the root dir of my docker-compose file

What is missing, imho:
- documentation: the current readme and docs do not make explicit the differences in behaviour that exist between running lazydocker on the host and running it within a container
- docs or changes to the existing lazydocker container so that it is easier to use it in a way that it can find an existing docker-compose project on the host
- an 'easy way' to allow lazydocker to filter out unwanted images/services/containers by usage of tags