If you could not use a package manager e.g. yum/apt what which OS would you choose?

tgl

alpine linux / apk

angstrom

@rajprakash said:

@angstrom said:
I remember compiling 2.0.x kernels on a i486 ThinkPad with 16 MB of RAM. It wasn't super fast, but not painfully slow, either.

Bah. 1.9 kernel compiles on 386 hardware ran overnight!
Edit: I think it was after around the 1.9 series that I moved over to Debian Bo, which was the first time I had a 2.0 series kernel. Dang that makes me feel old.

Well, you win. I never ran Linux on a i386!

souen

Debian minimal, or if not feasible, Alpine Linux as a second choice.

InceptionHosting

Based on available automation it’s looking like a minimal Debian image is the way to go.

iandk

The containers would be NAT/v6?

InceptionHosting

@iandk said:
The containers would be NAT/v6?

yup

InceptionHosting

Infact I have decided I am going to get started on that today.

The current VZ7 Debian template I have is about as minimal as possible already

Included packages:
#debian10
apt
openssh-client
openssh-server
wget
nano
iputils-ping

InceptionHosting

So having actually played with this, and experimented with real world use, no package manager in 2020 is not going to be an experience anyone would be interested, it took me an hour to satisfy the dependencies of gcc and that was using dpkg.

Looks like the best combo is 32mb ram and 64mb vswap, just about allows apt to run on a debian 10 container.

WSS

That would be perfectly adequate with Alpine, you know...

InceptionHosting

@WSS said:
That would be perfectly adequate with Alpine, you know...

The issue is I cannot create/maintain an alpine template for vituozzo 7.

maybe I could make an auto conversion script and inject it in to the template.

InceptionHosting

@WSS said:
That would be perfectly adequate with Alpine, you know...

With 32MB even alpine struggles it seems on vz7.

48MB however seems to be the sweet spot.

This might just work out.

WSS

@AnthonySmith said:

@WSS said:
That would be perfectly adequate with Alpine, you know...

With 32MB even alpine struggles it seems on vz7.

48MB however seems to be the sweet spot.

This might just work out.

If you build it using the virt-build, and just run with your VZ7 kernel it should be good enough for anyone who actually wants to do something with it.

WSS

This will inject on VZ6; might need to change to get it to bootstrap with 7. Not a fan of how it's done, but evidently it works.

https://gist.github.com/trimsj/c1fefd650b5f49ceb8f3efc1b6a1404d

yoursunny

@AnthonySmith said:
nano

I want to apt purge nano but there's no apt.

InceptionHosting

@WSS said:
This will inject on VZ6; might need to change to get it to bootstrap with 7. Not a fan of how it's done, but evidently it works.

https://gist.github.com/trimsj/c1fefd650b5f49ceb8f3efc1b6a1404d

yep, tested it on vz7 works fine.

I will try and find some time tomorrow, I was going to be fence posting but it looks like its going to rain all day.

I should just be able to extract the hds file from the debain 8 tar.lz4 template (the smallest one) and ploop mount it and insert a first boot script to run that, it takes about 2 - 3 minutes to run MAX so should work fine.

WSS

Ploop is still a thing in 7? I thought both that and SymFS were gonna go to the dump.

I've built an OVZ Alpine container with marginal effort before. Just be aware it can't sort properly so it's going to install 3.9

InceptionHosting

nope they stuck with ploop, I don't expect it to go anywhere soon.

Something to do with the opimised ext4 for CS for virtuozzo 7 cluster nodes.

Personally I truly hate it but it sure is a hell of a lot less problematic than it used to be.

simfs is a thing of the past.

WSS

@AnthonySmith said:
Something to do with the opimised ext4 for CS for virtuozzo 7 cluster nodes.

Nothing quite like more corrupt systems.