looking for guidance on writing 1-day "docker" training course
i hope sincerely that this post is not inappropriate for this list -- i'm looking for just *general* advice on what would constitute a decent yet intense 1-day training course on (ahem) "docker." by way of intro, i've been an open source trainer since the early 90s (anyone remember SCO UNIX? :-), and i've been (and am) an authorized trainer for some red hat courses. recently, some of my regular clients are asking for (you guessed it) classes in "docker" and kubernetes, so here's my plan. when a client asks for "docker" training, i just mentally map that to "i want to know how work with containers", and i would just use the fedora "podman" and "podman-docker" packages, take two minutes to explain, and go from there. i see no reason to mess with docker when podman exists. based on my research, it *appears* that i can cover containers and container management in one (admittedly busy) day, without ever getting into kubernetes -- that's a topic for another day. i've already got what looks like a reasonable outline -- i'm simply curious as to what content people on this list would think is a *must-have* for a 1-day intro container course. (aside: i'm not asking for people to write any content for me -- just bullet points that i might overlook.) i did poke around the net to see who else is offering similar courses to check out their outlines and prices, and there's just one site that i think might amuse/horrify people here. it turns out that, here in ottawa, there is a company that i've seen before offering courses comparable to mine, but for astronomically high prices. what the heck ... i'll just link to it: https://www.nobleprog.ca/cc/rancheros?type=classroom&participants=1&how=public that's $4045 (CAD) per student for a one-day course ... i have no idea why anyone would register for a 1-day intro docker course at that price but ... whatever. in any event, i want to design a 1-day intro course that i plan on offering on (naturally) fedora using podman (and maybe a bit of buildah), and all of that content will go up on my publicly-accessible wiki so anyone can read it. so ... if anyone has pointers to existing course outlines, or just topics that i really better not skip, drop me a note, and i'm going to see how much i can pack into one day of intro container training. rday p.s. followup courses will also ideally be offered on fedora, so i'll be covering podman and buildah and skopeo and ... you get the idea. -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ========================================================================
Hi Robert, I think this mail list is a perfect place to at the very least start up the discussion. Unfortunately the folks with probably the best answers are at conferences and/or are doing the PTO thing so they might not check in for a bit. It would be good to hear from Scott McCarty, Dan Walsh and William Henry who've done a fair amount of presentations at conferences. Just off the top of my head: o What are Containers o The container applications o Quick intro to Buildah o Deeper intro to Podman (Podman uses Buildah when it does `podman build`). o Introduction to Dockerfiles o Building a Container image o Touch on Docker and OCI formats o Building a container o Intro to container registries o Quay.io o Docker.io o Build your own registry o Pulling and Pushing to a Container Registry o Rootless Podman o Security features of Podman At least a start there. For a little deeper dive you could check out these resources: o https://github.com/containers/libpod/tree/master/docs/tutorials - Intro and Rootless tutorials for Podman o Replacing Docker with Podman Demo - https://github.com/containers/Demos/tree/master/running/ReplacingDocker o Security Demo - https://github.com/containers/Demos/tree/master/security o https://podman.io/talks/ - Slides from a few of the talks that might prove useful. That should get you going. Feel free to re-ping here or hit me up directly if you'd like, t On 08/15/2019 01:21 PM, Robert P. J. Day wrote:
i hope sincerely that this post is not inappropriate for this list -- i'm looking for just *general* advice on what would constitute a decent yet intense 1-day training course on (ahem) "docker."
by way of intro, i've been an open source trainer since the early 90s (anyone remember SCO UNIX? :-), and i've been (and am) an authorized trainer for some red hat courses. recently, some of my regular clients are asking for (you guessed it) classes in "docker" and kubernetes, so here's my plan.
when a client asks for "docker" training, i just mentally map that to "i want to know how work with containers", and i would just use the fedora "podman" and "podman-docker" packages, take two minutes to explain, and go from there. i see no reason to mess with docker when podman exists.
based on my research, it *appears* that i can cover containers and container management in one (admittedly busy) day, without ever getting into kubernetes -- that's a topic for another day. i've already got what looks like a reasonable outline -- i'm simply curious as to what content people on this list would think is a *must-have* for a 1-day intro container course.
(aside: i'm not asking for people to write any content for me -- just bullet points that i might overlook.)
i did poke around the net to see who else is offering similar courses to check out their outlines and prices, and there's just one site that i think might amuse/horrify people here. it turns out that, here in ottawa, there is a company that i've seen before offering courses comparable to mine, but for astronomically high prices. what the heck ... i'll just link to it:
https://www.nobleprog.ca/cc/rancheros?type=classroom&participants=1&how=public
that's $4045 (CAD) per student for a one-day course ... i have no idea why anyone would register for a 1-day intro docker course at that price but ... whatever.
in any event, i want to design a 1-day intro course that i plan on offering on (naturally) fedora using podman (and maybe a bit of buildah), and all of that content will go up on my publicly-accessible wiki so anyone can read it.
so ... if anyone has pointers to existing course outlines, or just topics that i really better not skip, drop me a note, and i'm going to see how much i can pack into one day of intro container training.
rday
p.s. followup courses will also ideally be offered on fedora, so i'll be covering podman and buildah and skopeo and ... you get the idea.
Yes, I think this is a good idea. Intro to Containers could definitely take up a day. Red Hat offers a 2 hour lab at each Red Hat summit, that really digs deap into container security. It is self guided and most students really like it. Scott McCarty has a 7/8 Self Paced labs that dig deep into containers. On 8/16/19 7:23 PM, Tom Sweeney wrote:
Hi Robert,
I think this mail list is a perfect place to at the very least start up the discussion. Unfortunately the folks with probably the best answers are at conferences and/or are doing the PTO thing so they might not check in for a bit. It would be good to hear from Scott McCarty, Dan Walsh and William Henry who've done a fair amount of presentations at conferences.
Just off the top of my head:
o What are Containers
o The container applications
o Quick intro to Buildah
o Deeper intro to Podman (Podman uses Buildah when it does `podman build`).
o Introduction to Dockerfiles
o Building a Container image o Touch on Docker and OCI formats
o Building a container
o Intro to container registries o Quay.io o Docker.io o Build your own registry
o Pulling and Pushing to a Container Registry
o Rootless Podman
o Security features of Podman
At least a start there. For a little deeper dive you could check out these resources:
o https://github.com/containers/libpod/tree/master/docs/tutorials - Intro and Rootless tutorials for Podman
o Replacing Docker with Podman Demo - https://github.com/containers/Demos/tree/master/running/ReplacingDocker
o Security Demo - https://github.com/containers/Demos/tree/master/security
o https://podman.io/talks/ - Slides from a few of the talks that might prove useful.
That should get you going. Feel free to re-ping here or hit me up directly if you'd like,
t
On 08/15/2019 01:21 PM, Robert P. J. Day wrote:
i hope sincerely that this post is not inappropriate for this list -- i'm looking for just *general* advice on what would constitute a decent yet intense 1-day training course on (ahem) "docker."
by way of intro, i've been an open source trainer since the early 90s (anyone remember SCO UNIX? :-), and i've been (and am) an authorized trainer for some red hat courses. recently, some of my regular clients are asking for (you guessed it) classes in "docker" and kubernetes, so here's my plan.
when a client asks for "docker" training, i just mentally map that to "i want to know how work with containers", and i would just use the fedora "podman" and "podman-docker" packages, take two minutes to explain, and go from there. i see no reason to mess with docker when podman exists.
based on my research, it *appears* that i can cover containers and container management in one (admittedly busy) day, without ever getting into kubernetes -- that's a topic for another day. i've already got what looks like a reasonable outline -- i'm simply curious as to what content people on this list would think is a *must-have* for a 1-day intro container course.
(aside: i'm not asking for people to write any content for me -- just bullet points that i might overlook.)
i did poke around the net to see who else is offering similar courses to check out their outlines and prices, and there's just one site that i think might amuse/horrify people here. it turns out that, here in ottawa, there is a company that i've seen before offering courses comparable to mine, but for astronomically high prices. what the heck ... i'll just link to it:
https://www.nobleprog.ca/cc/rancheros?type=classroom&participants=1&how=public
that's $4045 (CAD) per student for a one-day course ... i have no idea why anyone would register for a 1-day intro docker course at that price but ... whatever.
in any event, i want to design a 1-day intro course that i plan on offering on (naturally) fedora using podman (and maybe a bit of buildah), and all of that content will go up on my publicly-accessible wiki so anyone can read it.
so ... if anyone has pointers to existing course outlines, or just topics that i really better not skip, drop me a note, and i'm going to see how much i can pack into one day of intro container training.
rday
p.s. followup courses will also ideally be offered on fedora, so i'll be covering podman and buildah and skopeo and ... you get the idea.
_______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io
Thanks for the plug Dan. Robert, this is a great place to discuss this. Here's a draft agenda of what I have been working from for my container internals labs [1]. Just to give you a peak into my brain :-) I have implemented #1, #2, #3, #4 and #5 in the Basics, and #3 and #4 in the Advanced section, but could flesh out WAY more, just been constrained by time/wants :-) Basics 1. Introduction 2. Container Images - Red Hat base images, rhscl image, RHOAR, partner tools (scanners), security (signing, etc 3. Container Registries - quay.io/quay 4. Container Hosts - Red Hat CoreOS 5. Container Orchestration - OpenShift Advanced Container Internals 1. Intermediate Architecture 2. Advanced Architecture 3. Container Standards - OCI and why it helps customers 4. Container Ecosystem - Buildah/CRI-O/etc 5. Production Image Builds 6. Container Performance - plenty around upstream Kube work with Shak's team, and down into the kernel with overlayfs, etc 7. Container Security - including ecosystem and partners 8. Container Networking - plenty to plug including ecosystem and partners 9. Container Storage - all of the work RH does from OpenShift down to RHEL/CoreOS down to Gluster (very good testing story). Block storage (from Hitachi - partner story), etc. [1]: https://learn.openshift.com/subsystems/ On Sat, Aug 17, 2019 at 8:06 AM Daniel Walsh <dwalsh@redhat.com> wrote:
Yes, I think this is a good idea.
Intro to Containers could definitely take up a day. Red Hat offers a 2 hour lab at each Red Hat summit, that really digs deap into container security. It is self guided and most students really like it.
Scott McCarty has a 7/8 Self Paced labs that dig deep into containers.
On 8/16/19 7:23 PM, Tom Sweeney wrote:
Hi Robert,
I think this mail list is a perfect place to at the very least start up the discussion. Unfortunately the folks with probably the best answers are at conferences and/or are doing the PTO thing so they might not check in for a bit. It would be good to hear from Scott McCarty, Dan Walsh and William Henry who've done a fair amount of presentations at conferences.
Just off the top of my head:
o What are Containers
o The container applications
o Quick intro to Buildah
o Deeper intro to Podman (Podman uses Buildah when it does `podman build`).
o Introduction to Dockerfiles
o Building a Container image o Touch on Docker and OCI formats
o Building a container
o Intro to container registries o Quay.io o Docker.io o Build your own registry
o Pulling and Pushing to a Container Registry
o Rootless Podman
o Security features of Podman
At least a start there. For a little deeper dive you could check out these resources:
o https://github.com/containers/libpod/tree/master/docs/tutorials - Intro and Rootless tutorials for Podman
o Replacing Docker with Podman Demo - https://github.com/containers/Demos/tree/master/running/ReplacingDocker
o Security Demo - https://github.com/containers/Demos/tree/master/security
o https://podman.io/talks/ - Slides from a few of the talks that might prove useful.
That should get you going. Feel free to re-ping here or hit me up directly if you'd like,
t
On 08/15/2019 01:21 PM, Robert P. J. Day wrote:
i hope sincerely that this post is not inappropriate for this list -- i'm looking for just *general* advice on what would constitute a decent yet intense 1-day training course on (ahem) "docker."
by way of intro, i've been an open source trainer since the early 90s (anyone remember SCO UNIX? :-), and i've been (and am) an authorized trainer for some red hat courses. recently, some of my regular clients are asking for (you guessed it) classes in "docker" and kubernetes, so here's my plan.
when a client asks for "docker" training, i just mentally map that to "i want to know how work with containers", and i would just use the fedora "podman" and "podman-docker" packages, take two minutes to explain, and go from there. i see no reason to mess with docker when podman exists.
based on my research, it *appears* that i can cover containers and container management in one (admittedly busy) day, without ever getting into kubernetes -- that's a topic for another day. i've already got what looks like a reasonable outline -- i'm simply curious as to what content people on this list would think is a *must-have* for a 1-day intro container course.
(aside: i'm not asking for people to write any content for me -- just bullet points that i might overlook.)
i did poke around the net to see who else is offering similar courses to check out their outlines and prices, and there's just one site that i think might amuse/horrify people here. it turns out that, here in ottawa, there is a company that i've seen before offering courses comparable to mine, but for astronomically high prices. what the heck ... i'll just link to it:
https://www.nobleprog.ca/cc/rancheros?type=classroom&participants=1&how=public
that's $4045 (CAD) per student for a one-day course ... i have no idea why anyone would register for a 1-day intro docker course at that price but ... whatever.
in any event, i want to design a 1-day intro course that i plan on offering on (naturally) fedora using podman (and maybe a bit of buildah), and all of that content will go up on my publicly-accessible wiki so anyone can read it.
so ... if anyone has pointers to existing course outlines, or just topics that i really better not skip, drop me a note, and i'm going to see how much i can pack into one day of intro container training.
rday
p.s. followup courses will also ideally be offered on fedora, so i'll be covering podman and buildah and skopeo and ... you get the idea.
_______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io
-- -- Scott McCarty, RHCA Product Management - Containers, Red Hat Enterprise Linux & OpenShift Email: smccarty@redhat.com Phone: 312-660-3535 Cell: 330-807-1043 Web: http://crunchtools.com Have questions on Red Hat UBI? Check out the official FAQ: https://red.ht/2yaUcez
On Sat, 17 Aug 2019, Daniel Walsh wrote:
Just off the top of my head:
o What are Containers
o The container applications
o Quick intro to Buildah
o Deeper intro to Podman (Podman uses Buildah when it does `podman build`).
... snip ... i'm going to follow up on my earlier post with a thought that might provoke a reaction but, what the heck ... (i'm free associating here so, be warned ...) i've designed and delivered a *bunch* of linux/linux-related courses, and one of the things that seems to really, really, really set the stage properly early on is to list the components to be covered, and map those components *specifically* to the red hat/fedora packages that provide them. it may sound weird but, in the relevant courses, students seem to grasp the "big picture" more quickly if one not only lists the concepts to be covered, but maps that to actual fedora (my OS of choice) packages, along with what each package provides. let me give an example. if i'm going to teach a course on containers on fedora (which is my plan), it would be easy to just: $ sudo dnf group install --with-optional "container management" and go from there. but my experience is that it's clearer if one starts with the *minimal* set of packages to get started and, as the class progresses, one by one, installs each additional package only when necessary, while explaining what that new package brings to the table. so, after displaying the various components of container technology, i would start with only podman (and, sure, podman-docker) installed, and cover what that allows one to do. once that's done, introduce and install "buildah", and work with that. after that, skopeo, i guess, and so on, and so on. mapping each feature to a separate package really drives home the idea that these are different features that can be installed and worked with separately. over the next day or two, i'm going to flesh this out and put it all on a wiki page to make it clearer. i guess what i'm talking about here is explaining the entire container "ecosystem", and mapping that to the (fedora/RH) packages that support it. thoughts? rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ========================================================================
On 08/18/2019 05:29 PM, Robert P. J. Day wrote:
On Sat, 17 Aug 2019, Daniel Walsh wrote:
Just off the top of my head:
o What are Containers
o The container applications
o Quick intro to Buildah
o Deeper intro to Podman (Podman uses Buildah when it does `podman build`). ... snip ...
i'm going to follow up on my earlier post with a thought that might provoke a reaction but, what the heck ... (i'm free associating here so, be warned ...)
i've designed and delivered a *bunch* of linux/linux-related courses, and one of the things that seems to really, really, really set the stage properly early on is to list the components to be covered, and map those components *specifically* to the red hat/fedora packages that provide them.
it may sound weird but, in the relevant courses, students seem to grasp the "big picture" more quickly if one not only lists the concepts to be covered, but maps that to actual fedora (my OS of choice) packages, along with what each package provides. let me give an example.
if i'm going to teach a course on containers on fedora (which is my plan), it would be easy to just:
$ sudo dnf group install --with-optional "container management"
and go from there. but my experience is that it's clearer if one starts with the *minimal* set of packages to get started and, as the class progresses, one by one, installs each additional package only when necessary, while explaining what that new package brings to the table.
so, after displaying the various components of container technology, i would start with only podman (and, sure, podman-docker) installed, and cover what that allows one to do.
once that's done, introduce and install "buildah", and work with that. after that, skopeo, i guess, and so on, and so on. mapping each feature to a separate package really drives home the idea that these are different features that can be installed and worked with separately.
over the next day or two, i'm going to flesh this out and put it all on a wiki page to make it clearer. i guess what i'm talking about here is explaining the entire container "ecosystem", and mapping that to the (fedora/RH) packages that support it.
thoughts?
rday
_______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io
Robert, Your approach sounds entirely reasonable to me. As far as how/when to introduce Buildah, I'll leave that up to you. I just wanted to make you aware that Podman vendors in Buildah and then calls the API's for the actual building of the containers when it does `podman build`. The point that James brought up about the latest/greatest Buildah possibly not being the same as the one used by Podman is true. However, just before we release a new Podman we create a new version of Buildah and do a fresh vendoring into Podman. If you want to figure out what version of Buildah your Podman is using, you can use this command: # podman info | grep Buildah BuildahVersion: 1.9.0 One other small note in case it matters, Buildah and Podman use the --layers option differently. By default Podman build does this 'podman build --layers=true' while by default Buildah does `buildah --layers=false`. I bring this up only because with some Dockerfiles you will get different resulting images if you use one tool over the other due to the layers option being set differently. Hope that helps, t
(while my plan is to spend the upcoming weekend whipping a lot of this into shape, i'll address this ... man, i'm thinking i'm gonna need a bigger boat.) On Tue, 20 Aug 2019, Tom Sweeney wrote: ... big snip of mine ...
Robert,
Your approach sounds entirely reasonable to me. As far as how/when to introduce Buildah, I'll leave that up to you.
that would happen partway through that first day ... my tendency is to spend the early time instructing on how to simply *use* the technology before creating any new instances. the instant one starts to build their own images is the obvious place to explain that (for the most part) "podman build == buildah" and install buildah and go from there.
I just wanted to make you aware that Podman vendors in Buildah and then calls the API's for the actual building of the containers when it does `podman build`. The point that James brought up about the latest/greatest Buildah possibly not being the same as the one used by Podman is true. However, just before we release a new Podman we create a new version of Buildah and do a fresh vendoring into Podman.
If you want to figure out what version of Buildah your Podman is using, you can use this command:
# podman info | grep Buildah BuildahVersion: 1.9.0
One other small note in case it matters, Buildah and Podman use the --layers option differently. By default Podman build does this 'podman build --layers=true' while by default Buildah does `buildah --layers=false`. I bring this up only because with some Dockerfiles you will get different resulting images if you use one tool over the other due to the layers option being set differently.
Hope that helps,
yes, it's just that sort of detail that one should be aware of to avoid "hmmmmm, that doesn't seem quite right" confusion that could result. anyway, i still need to go through those early references to start laying out my idea of that 1-day class. there is no shortage of content one could pack in there. rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ========================================================================
Den 2019-08-20 kl. 15:23, skrev Robert P. J. Day:
On Tue, 20 Aug 2019, Tom Sweeney wrote:
... big snip of mine ...
Robert,
Your approach sounds entirely reasonable to me. As far as how/when to introduce Buildah, I'll leave that up to you.
that would happen partway through that first day ... my tendency is to spend the early time instructing on how to simply *use* the technology before creating any new instances. the instant one starts to build their own images is the obvious place to explain that (for the most part) "podman build == buildah" and install buildah and go from there.
That should probably be "podman build == buildah bud", for Day One. (i.e. when focusing on podman, rather than introducing another tool) The other commands and life-beyond-Dockerfile can come at a later stage. Maybe it doesn't even have to mentioned, and be more like "conmon" ? /Anders
Are you going to cover "podman-remote" and varlink anything, or is that out of scope given the Fedora focus ? Although Fedora might possibly be the *only* place that the resolver is available, or at least where it used to be... https://copr.fedorainfracloud.org/coprs/g/varlink/varlink/packages/ Starting to think that it might be easier to just use "ssh sudo podman" ? /Anders Den 2019-08-18 kl. 23:29, skrev Robert P. J. Day:
On Sat, 17 Aug 2019, Daniel Walsh wrote:
Just off the top of my head:
o What are Containers
o The container applications
o Quick intro to Buildah
o Deeper intro to Podman (Podman uses Buildah when it does `podman build`). ... snip ...
i'm going to follow up on my earlier post with a thought that might provoke a reaction but, what the heck ... (i'm free associating here so, be warned ...)
i've designed and delivered a *bunch* of linux/linux-related courses, and one of the things that seems to really, really, really set the stage properly early on is to list the components to be covered, and map those components *specifically* to the red hat/fedora packages that provide them.
it may sound weird but, in the relevant courses, students seem to grasp the "big picture" more quickly if one not only lists the concepts to be covered, but maps that to actual fedora (my OS of choice) packages, along with what each package provides. let me give an example.
if i'm going to teach a course on containers on fedora (which is my plan), it would be easy to just:
$ sudo dnf group install --with-optional "container management"
and go from there. but my experience is that it's clearer if one starts with the *minimal* set of packages to get started and, as the class progresses, one by one, installs each additional package only when necessary, while explaining what that new package brings to the table.
so, after displaying the various components of container technology, i would start with only podman (and, sure, podman-docker) installed, and cover what that allows one to do.
once that's done, introduce and install "buildah", and work with that. after that, skopeo, i guess, and so on, and so on. mapping each feature to a separate package really drives home the idea that these are different features that can be installed and worked with separately.
over the next day or two, i'm going to flesh this out and put it all on a wiki page to make it clearer. i guess what i'm talking about here is explaining the entire container "ecosystem", and mapping that to the (fedora/RH) packages that support it.
thoughts?
rday
On Fri, 16 Aug 2019, Tom Sweeney wrote:
o Deeper intro to Podman (Podman uses Buildah when it does `podman build`).
i'm going to be just a wee bit pedantic here, in that i don't think podman uses buildah doing "podman build", as i just did a "podman build" after explicitly removing the buildah package to test that very thing. i will explain shortly why that matters to me -- give me time to collect my thoughts. rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ========================================================================
On Sun, Aug 18, 2019, at 2:43 PM, Robert P. J. Day wrote:
On Fri, 16 Aug 2019, Tom Sweeney wrote:
o Deeper intro to Podman (Podman uses Buildah when it does `podman build`).
i'm going to be just a wee bit pedantic here, in that i don't think podman uses buildah doing "podman build", as i just did a "podman build" after explicitly removing the buildah package to test that very thing.
It's a but ugly, but it seems that right now, each of the container tools embeds a copy of each of the other tools, often in slightly different versions... so podman build is using its internal version if buildah that may have different features and bugs than the version you get when using buildah directly on the command line. V/r, James Cassell
On Sun, 18 Aug 2019, James Cassell wrote:
On Sun, Aug 18, 2019, at 2:43 PM, Robert P. J. Day wrote:
On Fri, 16 Aug 2019, Tom Sweeney wrote:
o Deeper intro to Podman (Podman uses Buildah when it does `podman build`).
i'm going to be just a wee bit pedantic here, in that i don't think podman uses buildah doing "podman build", as i just did a "podman build" after explicitly removing the buildah package to test that very thing.
It's a but ugly, but it seems that right now, each of the container tools embeds a copy of each of the other tools, often in slightly different versions... so podman build is using its internal version if buildah that may have different features and bugs than the version you get when using buildah directly on the command line.
exactly. i'm not making any value judgments, i just want to be able to describe it accurately. more pedantic nitpickery shortly ... rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ========================================================================
On Sun, 18 Aug 2019, James Cassell wrote:
On Sun, Aug 18, 2019, at 2:43 PM, Robert P. J. Day wrote:
On Fri, 16 Aug 2019, Tom Sweeney wrote:
o Deeper intro to Podman (Podman uses Buildah when it does `podman build`).
i'm going to be just a wee bit pedantic here, in that i don't think podman uses buildah doing "podman build", as i just did a "podman build" after explicitly removing the buildah package to test that very thing.
It's a but ugly, but it seems that right now, each of the container tools embeds a copy of each of the other tools, often in slightly different versions... so podman build is using its internal version if buildah that may have different features and bugs than the version you get when using buildah directly on the command line.
right, that's what i assumed; i'm just saying that that is useful information to know if, for example, the claim is that "podman uses buildah for doing its builds," when, in fact, it is using some (probably stripped down) internal version. definite potential for confusion there if one is unaware of that. another example of that coming shortly unless i unconfuse myself first. rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ========================================================================
On Mon, Aug 19, 2019 at 1:03 PM Robert P. J. Day <rpjday@crashcourse.ca> wrote:
On Sun, 18 Aug 2019, James Cassell wrote:
On Sun, Aug 18, 2019, at 2:43 PM, Robert P. J. Day wrote:
On Fri, 16 Aug 2019, Tom Sweeney wrote:
o Deeper intro to Podman (Podman uses Buildah when it does `podman build`).
i'm going to be just a wee bit pedantic here, in that i don't think podman uses buildah doing "podman build", as i just did a "podman build" after explicitly removing the buildah package to test that very thing.
It's a but ugly, but it seems that right now, each of the container tools embeds a copy of each of the other tools, often in slightly different versions... so podman build is using its internal version if buildah that may have different features and bugs than the version you get when using buildah directly on the command line.
right, that's what i assumed; i'm just saying that that is useful information to know if, for example, the claim is that "podman uses buildah for doing its builds," when, in fact, it is using some (probably stripped down) internal version. definite potential for confusion there if one is unaware of that.
I opened a PR for Buildah's README to make that explicit [1]. Thanks for pointing this out. [1] https://github.com/containers/buildah/pull/1801
another example of that coming shortly unless i unconfuse myself first.
rday
--
======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca
Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== _______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io
participants (7)
-
Anders F Björklund -
Daniel Walsh -
James Cassell -
Robert P. J. Day -
Scott McCarty -
Tom Sweeney -
Valentin Rothberg