News for hackers. Stuff that matters.
Re:Linux containers in 500 lines of code (2016) by tenuousemphasis on Thursday March 10, 2022 @08:27AM (#30626629)
This is so clever. I love the use of comments and parsing the source file for those comments as a way of displaying help.
Re:Linux containers in 500 lines of code (2016) by LanternLight83 on Thursday March 10, 2022 @11:03AM (#30628424)
I think they're going for the minimal line count by in lining the docstrings. In some of my own scripts, I've lifted an idea that I saw in the wild where your Usage header and function docstrings are just prefixed with '#/', a more aesthetic and equally unlikely string (which also looks good in blocks, so it could even be restricted to newlines that just are comments, letting the line count breath a but and removing any worry of accidentally using that sequence in code). Our help function would then just 'grep w/e $BASH_SOURCE | cut w/e'.
Re:Linux containers in 500 lines of code (2016) by pmarreck on Thursday March 10, 2022 @10:18AM (#30627840)
is Docker married to btrfs?
Re:Linux containers in 500 lines of code (2016) by tyingq on Thursday March 10, 2022 @10:48AM (#30628210)
Docker defaults to overlay2, but supports btrfs and others: https://docs.docker.com/storage/storagedriver/select-storage...

"Bocker" uses btrfs only.

Re:Linux containers in 500 lines of code (2016) by pmarreck on Friday March 11, 2022 @01:25PM (#30643903)
I wish Docker had been kept as simple as possible. A Bocker that uses overlay2 could potentially be a Docker-like MVP.