It's impossible to work with docker containers without docker images. In this post I want to talk about what makes docker images possible: the ove...
For further actions, you may consider blocking this person and/or reporting abuse
Today I learned about OCI stuff (that is totally new to me) and what’s going on behinds the scene when I run
docker build. At first I thought it was a complex, custom-made, Docker-specific stuff. The way you broke it down two ordinary Linux commands made it much clearer for me what’s going on… it doesn’t look as scary as I thought now.Thanks for sharing!
Thank you! Glad it helped :)
1) *CLI examples aren't consistent. *
and then:
Imaging that noob reads it and the very first question is "What's the pactvm??"
Another important point is that the simple CTRL+C, CTRL+V of commands isn't working.
the
cd /tmp/overlay-exampleis missed. I can almost see how noob does just a
cdand
rm -rf *does the trick. Why not to put
rm -rf /tmp/overlay-example/*?
To sum it up, the article explains a really nice concept.. but in a very inconsistent and dangerous way.
Thank you. :)
I am not a newbie, or at least i do not consider myself one, and I was confused by pactvm... thinking it was some command that I had never seen before, but I was too lazy to do a search.
It s my login name. I removed it from most of the commands but forgot to remove it from some. I m so used to see my terminal that way I do not even notice it anymore 😅
I removed it. Thanks for the feedback
I think:
sudo umount /tmp/overlay-example/mount && rm -rf .*-->...&& rm -rf *Good catch, it was a typo. Thanks
No big deal, at least it throws an error. Not sure the feelings if the typo were
rm -rf /*:))Even if it was "/*" it would have thrown an error, unless you were running as root. Note that only the mount is sudo-ed and that privileges are not propagated to the other commands in the && condition. Try:
That being said, the boy scout rule applies: never run as root and never copy/paste random commands (especially the ones which require privilege escalation) without knowing what they do :)
One of the very early union file systems is Clearcase by Rational Software (now owned by IBM). A workspace is put together via a series of views (which are versioned software releases) overlaid upon one another. The software required modifying the Solaris Kernel and required very powerful CPUs to work well. You would make all your changes in the top layer and when it was time to commit you only had to specify what branch(es) to add those changes to - clearcase knew what had been changed.
en.wikipedia.org/wiki/Rational_Cle... .
That's interesting, I did not know that! Thanks for sharing it :)
Thanks for this article!
Amazing way of describing hard concepts.
Can I use this to create some slides for a talk?, of course giving the credits of the author.
Hi, thanks. Sure, you can use it.