News for hackers. Stuff that matters.
Re:Docker implemented in around 100 lines of bash by rtlfe on Saturday October 15, 2022 @04:36PM (#33218372)
> Don't know if it can be used as a proper Docker replacement

The readme says "I can make no guarantees that it won't trash your system", so yeah clearly not intended for real use.

Re:Docker implemented in around 100 lines of bash by jen20 on Saturday October 15, 2022 @05:10PM (#33218697)
Most software says that in the license too (even commercial software!) so it’s nice to see it front and center for once.
Re:Docker implemented in around 100 lines of bash by stjohnswarts on Saturday October 15, 2022 @05:43PM (#33218935)
that's why smart people always check this stuff out on spare machines and VMs.

Right?

... right?

Re:Docker implemented in around 100 lines of bash by counttheforks on Saturday October 15, 2022 @08:10PM (#33219865)
I typically run stuff inside of docker
Re:Docker implemented in around 100 lines of bash by yjftsjthsd-h on Saturday October 15, 2022 @09:18PM (#33220247)
And now I'm curious whether this would work inside a container or not. I know dind is a thing, but I don't recall whether it needs special hacks that bocker lacks.
Re:Docker implemented in around 100 lines of bash by chupasaurus on Saturday October 15, 2022 @09:39PM (#33220351)
It requires nearly full root access for the inner container runtime, thus it can trash your system.
Re:Docker implemented in around 100 lines of bash by kazinator on Sunday October 16, 2022 @12:45AM (#33221098)
Where does Docker guarantee that it won't trash your system?

See here: https://www.docker.com/legal/docker-terms-service/

Under EXCLUSION OF WARRANTIES and LIMITATION OF LIABILITY.

Here, Bocker is also a replacement for Docker in exactly the same sense: Bocker's simple statement "I can't guarantee it won't trash your system" is a concise alterantive to a wall of legalese.

Re:Docker implemented in around 100 lines of bash by kristopolous on Sunday October 16, 2022 @01:04AM (#33221166)
To be fair one is for demonstration purposes and the other is intended to be used. They seek the same protections regardless. It's kind of like how a $1,000 water filtration system wants the same legal protection that a $15 Brita does or heck, I'd assume if you got scammed with a fraudulent water filter that used orgone energy and crystals, it too would also want those legal protections.

You'd probably want to tread cautiously if someone doesn't use disclaimers - that's probably a more dangerous product.

Re:Docker implemented in around 100 lines of bash by kazinator on Sunday October 16, 2022 @02:02AM (#33221404)
Sure, but in this case both Bocker and Docker just orchestrate features of Linux, which is where all the risks and complexity lies.

To verify that Bocker adds no additional issues is a smaller job than verifying Docker in the same way.

If there is some problem in the actual containerization, Bocker and Docker will be equally affected.

Re:Docker implemented in around 100 lines of bash by okamiueru on Sunday October 16, 2022 @05:27AM (#33222344)
Isn't the argument presented here that just because two things have the same "no responsibility in event of failure"-clause does not mean likelihood of failure, robustness, battletesting, etc, are comparable? Or am I missing something
Re:Docker implemented in around 100 lines of bash by bottled_poe on Sunday October 16, 2022 @02:55AM (#33221648)
But.. it’s not a good alternative. This description is not as precise or as bounded as the “legalese” wording.
Re:Docker implemented in around 100 lines of bash by makapuf on Sunday October 16, 2022 @03:30AM (#33221844)
Well, I didn't read the legalese but read this short sentence. That makes it 1000% better for me right now, you can't abstract away the message channel. Maybe the best would be to have a short 10-line summary then the legally bounding legalese. (Edit: nonsense spelling error)
Re:Docker implemented in around 100 lines of bash by anderspitman on Sunday October 16, 2022 @11:33AM (#33224363)
Should probably run it in a VM just to be safe