bigpod

5 ms·

1.
by bigpod 7mo ago
nixos may have a simpler moder on paper the implementation of it is so backwards that it ruins everything, and once you implement the model you see its not simpler and your conclussion is wrong nix and nixos has a lot to learn from bootc, l
2.
by bigpod 7mo ago
yea it switched to a in general much better distribution method then custom https server, for one thing authentication is built in something many of these https solutions forget(look at every linux package manager)
3.
by bigpod 7mo ago
system extensions are just as usable on bootc based systems but bootc based systems allow for much simpler composition, you dont have to know about all the intricacies of linux filesystem tree to install a set of packges for your own image
4.
by bigpod 3y ago
yes it is un update its not a container deployment and this is in no way connected to flatpak outside of ostree well my experiance and experiance of many other people say otherwise and most wide reaching example look at how a single miss co
5.
by bigpod 3y ago
not realy look for a more detailed anwser on one of your other comments under the parent of this one
6.
by bigpod 3y ago
your normal distro does updates by pulling every package on your system and swapping files mid running this can cause miriad of issues just by doing it and another miriad if update is stopped mid updating(not always but sometimes). So this
7.
by bigpod 3y ago
kinda the point
8.
by bigpod 3y ago
Cloud native is a set of principles with which you develop and build software to make it less likely to break and be more conducive to rapid iteration(In theory you dont even need to deploy your app to cloud to be cloud native) ublue and pr
9.
by bigpod 3y ago
no project bluefin doesnt sell a piece of hardware but chromebook is far more known as a technology then the operating system it runs ChromeOS(based on gentoo) so its wording targeted at layman
10.
by bigpod 3y ago
thanks to distrobox
11.
by bigpod 3y ago
its more applying cloud native principles (principles that work very well in server side even if you don't use cloud) to create stable and well made "next-gen" distros
12.
by bigpod 3y ago
been using bluefin while it was in beta for almost a year and for me it was very easy to move to it as my development workflow is nothing like most and i heavily utilize podman containers on the outset and not system packager or flatpak. th
13.
by bigpod 3y ago
at the end of the day its just set of principles
14.
by bigpod 3y ago
same principles, Buzzword, Excitement
15.
by bigpod 3y ago
Totally agreed one man distros might not get maintained after release or two but: Behind Bluefin is a project called Universal blue which is a whole bunch of people with many interests, but biggest one being DevOps, devOps combined with its
16.
by bigpod 4y ago
your tests and your application knowledge should in some cases i essentialy ensure my whole app remains using --include-path flags so that i get a removal of you know things that i absolutly dont need.
17.
by bigpod 4y ago
one question is is possible in any kind of way that that passwd or any other binary that stays that you dont need has a security vulnarability that could if someone got into the container in one way or another(most likely your app) cause tr
18.
by bigpod 4y ago
i would disagree i use em in production apps, i configured it and it works if you do it blindly it happens that sometimes things break but if you configure it, it will work
19.
by bigpod 4y ago
essentialy yes
20.
by bigpod 4y ago
with good pipeline and knowledge about your app you should be able to ensure it works without much of a problem
21.
by bigpod 4y ago
use --include-path to ensure its in
22.
by bigpod 4y ago
its more about being more like people say as smaller by 200% isnt as understandable as 30 times smaller
23.
by bigpod 4y ago
this is not valid but its what people say 30 times smaller.
24.
by bigpod 4y ago
i have docker-slim in CICD completly automated seems to not have a problem as i ahve configure it per pipeline, maybe check out examples for docker-slim
25.
by bigpod 4y ago
docker-slim started at docker hackathon in 2015 and company behind Slim.AI has an extension for docker desktop in its marketplace.
26.
by bigpod 4y ago
this removes far more then multistage docker build ever would, do you need bash dash or passwd or many other binaries and files in image that are in by default no you dont only way to do anything simular to what docker-slim does is with scr
27.
by bigpod 4y ago
it sometimes doesnt work sure but thats why we have tests and test i minify all my containers nowdays and in most cases it works in those that it doesnt i figured out the pattern when and why for my apps and use include flags to ensure thin
28.
by bigpod 4y ago
yes that tends to be the problem with docker-slim as well that is why it includes flags like --include-path with which you can easily achive such fixes personaly i highly recommend as it works in most cases and gets rid of those vulnerablit
29.
by bigpod 4y ago
it is error prone somewhat but it has flags to allow you to fine tune what gets added back in. great thing is you can work with any base image and language including those that wont work with scratch
30.
by bigpod 4y ago
thats why you should test and if there are stuff htat needs to be included but arent and you know wont work fail the test and add --include-path to your docker-slim command to ensure something is added

More ›