Show HN: Bocker – Docker implemented in 100 lines of bash
41–50 of 89 posts
Re: Show HN: Bocker – Docker implemented in 100 lines of bash
#42Earlier quoted context omitted.
clustering and orchestration still sucks I don't see that changing until we get proper single-system imaging, location transparency, process and IPC migration, process checkpointing and RPC-based servers for representing network and local resources as objects (be they file-based or other) in our mainstream systems. These things only really caught on in the HPC and scientific computing spaces, where you've had distrib…
I ran an OpenMOSIX cluster as a hobby. The alternative was Beowulf (the meme of the day was "Imagine a Beowulf cluster of these things"). It seems the mainstream server industry has moved to more isolation rather than more interconnectedness, which is probably better for most public-facing systems.
Re: Show HN: Bocker – Docker implemented in 100 lines of bash
#43The author of "bocker" (not my bocker) has a great idea. I would learn from the script. Docker is not magic anymore.!!
Re: Show HN: Bocker – Docker implemented in 100 lines of bash
#44Re: Show HN: Bocker – Docker implemented in 100 lines of bash
#45Re: Show HN: Bocker – Docker implemented in 100 lines of bash
#46I'm missing something, what actually "executes" the command here echo "$2" > "$btrfs_path/$uuid/$uuid.cmd" Is something watching for .cmd? Is this some behavior of util-linux (for which, my few seconds couldn't find solid documentation on)?
The run command itself is executed next, inside of ip netns exec.
Re: Show HN: Bocker – Docker implemented in 100 lines of bash
#47I'm missing something, what actually "executes" the command here echo "$2" > "$btrfs_path/$uuid/$uuid.cmd" Is something watching for .cmd? Is this some behavior of util-linux (for which, my few seconds couldn't find solid documentation on)?
If my dry read of the code is correct, that line is for the "bocker ps" routine to be able to print the command later. The run command itself is executed next, inside of ip netns exec.
Re: Show HN: Bocker – Docker implemented in 100 lines of bash
#48Earlier quoted context omitted.
Dokku written in bash? (I am one the maintainers of dokku, which is written in bash).
I think he's suggesting creating a similar project to dokku, but instead of using Docker, use Bocker.
Though I don't think that is what he is asking for.
Re: Show HN: Bocker – Docker implemented in 100 lines of bash
#49Wow, Docker in 100 lines! It runs as root? Oh. It is written in bash? Oh. It needs a ton of manual setup? Oh. It doesn't actually implement the package format which is most of the point of Docker? Oh. So is it that easy to reimplement Docker? Despite the obvious snarky intent, it appears not.
Re: Show HN: Bocker – Docker implemented in 100 lines of bash
#50 echo 'nameserver 8.8.8.8' > "$btrfs_path/$uuid"/etc/resolv.conf
This is wrong on so many level that I don't know where to begin with.