ilmostro added a new comment to an issue you are following: `` >From the docker-docs https://docs.docker.com/engine/userguide/eng-image/baseimages/#create-a-full-image-using-tar A parent image is the image that your image is based on. It refers to the contents of the FROM directive in the Dockerfile. Each subsequent declaration in the Dockerfile modifies this parent image. Most Dockerfiles start from a parent image, rather than a base image. However, the terms are sometimes used interchangeably. A base image either has no FROM line in its Dockerfile, or has FROM scratch Given that docker is native to Linux, we should safely assume that the "host" OS is Linux or that users can build containers within a Linux VM or parent image. Furthermore, if that Linux distro is RPM-based, the approach outlined at https://github.com/moby/moby/blob/master/contrib/mkimage-yum.sh can be used to build an RPM-based container without a Parent Image. In other scenarios, such as on non-rpm-based distro hosts/systems, the Parent image might be relevant/necessary. As for systemd, that shouldn't be needed/used within the container. There's a redhat blog post that can also be referenced to get a better idea of the end-result: http://rhelblog.redhat.com/2017/03/13/introducing-the-red-hat-enterprise-linux-atomic-base-image/ `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/290 _______________________________________________ cloud mailing list -- cloud@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to cloud-leave@xxxxxxxxxxxxxxxxxxxxxxx
