I'm not so sure this is really a bug against docker itself or the packaging within Ubuntu necessarily. The two files mentioned are generated either by upstart (/run/container_type) or by systemd (/run/systemd/container). The 'official' ubuntu images don't appear to run with either one as the containers in docker are focused around isolating an application not an entire system. If the application deployed to a docker container requires the systemd or upstart services, then one would expect the service to be running as part of the image, however I suspect most services running within a docker container don't need those files.
If you are wanting to determine that you are running within a docker container, you could check the existence of a /.dockerenv file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1609087 Title: Ubuntu docker images should create /run/container_type & /run/systemd/container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1609087/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
