From b19f4ff2bdba961d7d088263b9ed950e26997875 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Sun, 21 Jul 2019 11:32:44 -0400 Subject: comment --- ...ent_5_45f48be3688d2879098cc72be334cb8d._comment | 26 ++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 doc/forum/Getting_Info_from_containers/comment_5_45f48be3688d2879098cc72be334cb8d._comment (limited to 'doc/forum') diff --git a/doc/forum/Getting_Info_from_containers/comment_5_45f48be3688d2879098cc72be334cb8d._comment b/doc/forum/Getting_Info_from_containers/comment_5_45f48be3688d2879098cc72be334cb8d._comment new file mode 100644 index 00000000..f94daf58 --- /dev/null +++ b/doc/forum/Getting_Info_from_containers/comment_5_45f48be3688d2879098cc72be334cb8d._comment @@ -0,0 +1,26 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 5""" + date="2019-07-21T15:18:51Z" + content=""" +This seems like a reasonable change to make, although I am not sure I +understand how you'd practially use it. + +But as far as how to implement it, you merely need to make an IsInfo +instance for Host (or for [Host]) and then each of the container properties +can add the Host of their container to the Info. + +Hmm, actually, this info is already provided in another way. +In Propellor.Types.Chroot there is a ChrootInfo that builds up a map from +chroot location to Host, and that gets added to the Info of the host where the +chroot is used. + +As well as being used for regular chroots, the systemd containers are based +on a chroot and so also use and provide it. Docker does not currently use +it though. It has a separate DockerInfo that also happens to include the +Host corresponding to the docker container. + +Anyway, I guess I'm a little bit unclear on what your original problem was, +it might help if you could restate it in more detail to see if this would +really help with it. +"""]] -- cgit v1.2.3