I think having the option to specify an alternate docker-compose file is a great idea. With that we can also put up some example compose files to show users what provisioner can do. For example opening up port ranges for services to bind and expose to the outer network. This is useful for visiting UI pages on browsers.
- Evans Luca Toscano <toscano.l...@gmail.com> 於 2022年1月8日 週六 下午7:42寫道： > Hi everybody, > > I filed a code review for the Docker provisioner in > https://github.com/apache/bigtop/pull/851, Masatake has already > reviewed it but since a lot of people use it I wanted to bring it to > your attention. The main issue that I found is that on recent OSes > like Debian 11, mounting /sys/fs/cgroup to the containers causes > systemd and dbus to fail when starting. The only explanation that I > can give is that cgroupsv2 are enabled by default, and recent enough > versions of Docker compose (10.20+) support them natively. If you have > a better and more precise explanation please let me know, otherwise > I'd like to merge the pull request during the next few days. The idea > is to have, as an experimental feature, a separate docker-compose.yml > config file that doesn't contain the /sys/fs/cgroup mountpoint, and > experiment with it. > > Let me know what you think :) > > Luca >
