smoochy

I'm not sure either, I've never even heard about toolbox. And systemd... Yeah. I never really cared about whether or not "it is", until configuring things started to get out of hand.

But you are not correct in assuming this is aiming for Linux - my next goal is adding BSD jails. I see absolutely no reason why different container engines would bother user with architecture, different APIs and apps etc. And, then, I think there's actually something, that although it sounds crazy, might work wonderfully on any OS, see my comment here: https://news.ycombinator.com/item?id=31625920

Well, I guess I'm really one of those people. There is no way I'm ever remembering correct arguments to `tar`. In fact, aliases or even the `untar` script that I have in the bashjazz/utils set... Like I would still be mentally trembling, wondering if it's really going to do what I expect it to. With respect to that, `gzip` is light years away. I have no idea why someone decided they need to ask users to enter four cli-arguments/flags in order for tar to do its job. Must have been a reason, it'd be interesting to look it up. But yes, everyone should pick their battles and `tar` ain't mine.

You're quite correct in addressing the issue, indeed, why wouldn't it just grab an image from Docker Hub and make it dock-compatible? And that's what I'm working on. See my comment here: https://news.ycombinator.com/item?id=31625086#31625750

Best ideas aren't always the first ones in the queue. Remember, I built it for myself first and never thought I'd do a release, so there was no point to it initially.

Indeed, you got the vibe just right. I wanted this tool-set to be time-proof. Been working "on my machine" for 1,5 years. I had to do some serious clean-up and re-writing so that it started working on other people's machines, but once you get it running - it does not break. I've long noticed that things that are simple - such as tiny scripts or libraries I'd write - would outlive larger projects I would work on. So these days I only try and write software that can last. Bash isn't perfectly portable, to be honest (FreeBSD doesn't even have it by default, and MacOSX has an outdated version of it), but what else? I've recently refreshed my memories of Perl, wrote a few scripts with it and, somehow, it felt harder to deal with than Bash...

Thank you, typo fixed. I think there are more. I usually do try and proof-read, but there's never enough time.

AUTHOR here, folks. If you have any questions that you're too lazy to email - I'll be checking on this thread for the next couple of hours.

Thank you. Yeah, I guess it's a matter of what you're used to. For me personally, I've never gotten used to Dockerfiles. It seemed like another configuration file format invented for nothing. With rules I had to remember. Entrypoint? Ugh. So I've just done everything in Bash, made it imply which container/image I want from $PWD and it saved me a ton of time. And, actually, I do tend to create/destroy containers quite often because of how easy it is (no editing files or even providing cli arguments to `dock`).

As for supporting VMs - you misunderstood. I meant support for other container engines. To me, it would most notably be BSD jails. In fact, if I get to it, I'd like to do something much more cool... Perhaps it would make sense to have a VM with FreeBSD running on a machine and then multiple BSD jails running inside - all managed by a relatively small tool-set, such as `dock` - I'd probably have to rename or fork it. But the cool part of it all is that containers won't even depend on an architecture, since they'd be running inside a VM.

Author here: it actually doesn't break. Been running it for 1,5 years. It's bash, there isn't much that can break. And it uses Docker cli with no hackery or experimental options.

The only thing I am working on right now: a way to avoid building special images for MacBooks or ARMs, but rather have a patch-tool (a bash script, essentially), which would pull any image you want from Docker Hub and then run patches on it (patches are also simple, readable Bash scripts which would work kind of like migrations for DBs), so that you will quickly have a Dock-compatible image and if you wanted a Python or a Ruby env you'd use an extra set of included patches or write your own.

It sounds more complex than it would actually work, honestly.

Indeed. This will probably be removed. The argument against --required-args is actually much simpler: it only makes sense to have groups of required arguments - such as when we either want -a -b -c or '-x -y -z', but it's pointless to demand to include any single argument that doesn't require an explicit value.

So, obviously, I think formatting (even if we talk about plaintext that isn't modified) is important and I do think a screenshot and maybe a short screencast - those are all important things. But suppose you couldn't display images or even link to them. How does one find the right words? I guess that's my question, yes. Words.

Sometimes yes, because in the end everyone here is trying to justify some kind of purpose, but in reality they forget that it's all music and dance and it doesn't have to arrive at a certain point. Upvoted.

I'm thinking mobile apps are a thing of the past. But writing a book is a hell of a job. I did it once, it was hard, as hell and the everybody pirated it.

I'm wrapping my head around what's the purpose of this.

I think it'd be impossible to do such a thing on a large scale with cash or credit cards/paypal, especially if it perates worldwide. High fees, many people unbanked, subject to lots of regulations depending on the jurisdiction. That would be a major pain in the ass. Projects like these is where Bitcoin shines.