Are there any downsides to doing this?
this post was submitted on 14 Jul 2023
116 points (93.3% liked)
Selfhosted
39435 readers
1 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
AFAIK it works by analyzing your docker image, checking whats actually used and then throwing out anything else.
For example if you use the Ubuntu base image you have a full minimal OS install. If you're now running a python server for example it's highly unlikely that you will need the perl interpreter that's in the default install so it can be thrown out.
It can get problematic if you want to run something that loads libraries or runs programs dynamically at runtime, since the tool can't easily detect them then and you need to manually intervene. Tried it once on a custom machine learning container and it kept throwing out parts that I actually needed, so I gave up in the end.
It's usefulness is also somewhat limited, since docker containers also share their base images. So if you have three containers running that are all based on Ubuntu 22.04 you will still only have to download it once
Great write up! That's everything exactly right. It's mostly useful to try and reduce the time it takes to pull images to run them. And also reduce the footprint of storing those in your registries.
It ptraces the main container process and cuts off unused files. It also fires some customizable HTTP requests to trigger any dynamically loading libraries. Clever idea. If I understand correctly, the problems that arise to me are:
- Undoubtedly some essential files will be omitted. Unless my image consists merely of
scratchand an executable, I can't imagine myself successfully covering all edge cases. - What about files that aren't loaded by HTTP requests?
I'm not shitting on this program at all. These are two problems that I'm sure they could solve or just tell straight up "we can't guarantee it'll work in XYZ scenarios. Don't use it if that's your use case". Then I saw that this is backed by some kinda SaaS with a domain that ends with .ai, and that explains why THAT FUCKING README IS WRITTEN like a FUCJik/INg MIND NUMBING LINKEDIN POST that my CEO could write bro what the fuck do you mean by simplifying the value of my digital assets in a seamless secure cost efficient way????? Who fucking cares??? ?WHat does your program ACTUALLY DO??????????
10000000s of seemingly AI-generated paragraphs going on and on about how convenient their product is, 1 measly line in a diagram that describes what it actually does. Again not to shit on the programmers at all, this is a great idea and I'm glad that it's being explored I just hate this industry I can't read another pile of gibberish like that. That ruined my night. Thanks for listening
COuldn't agree more on this! Honestly. I understand that people want hefty descriptions with few inputs on their side, but this is sad.
Anyways! Some of my python cronjobs that I run on my cluster don't have an exposed service, and I can still make it work just fine by passing along the --exec flag and the stuff that takes to run the app. The complicated part is to define properly your environment variables that are necessary to run your use-cases and make sure that you execute all the necessary files. It's not a solution that fits all, for sure! And I honestly don't use it for everything. It's a tool to be used in some use-cases
Oh there's an --exec flag as well? That's great. This seems like a totally viable solution for cases where the crux of the container is a small script, with a handful of decision branches so the surface area to cover is manageable, but it also needs to come in a non-alpine distro because I assume that's the hefty part that we're like to remove. But that's just off the top of my head, I'm sure there's more. It's genuinely a good idea and it deserves a respectful README as well :(
I can feel this reply. Cheers to a better weekend!
For a complex (i.e., larger) image, I would be concerned that I didn’t exercise all of my app’s functionality and something important might be stripped out of the image.
I use Alpine instead of Ubuntu when I’m concerned about image size.
Fair point! What I've done in my app to test out and ensure it works is a proper health endpoint that tests the use-cases of the app. So far it has been very good on keeping everything that I need on slimming.
Huh, I figured my containers were already as small as I could get them by using compiled go binaries in a distroless container. But it looks like there could still be some gains to be made!
Yep, same thing I found out! Crazy to see my already quite slim image being reduce all that much!
Crazy to see my already quite slim image being reduce all that much!
*size.original='1.0 GB' *
I mean.... I don't know what that does, of course, but I would rarely use "quite slim" to describe that :D
"size.original='66 MB' size.optimized='33 MB'"
This one's nice though
Yeah? I meant the 66MB one. The 1GB was an image that I just installed everything necessary to compile my code and run from the same image. I didn’t try to make it “right”. Nice to know I don’t have to worry about it though!
I love go on distroless, that sucker is like <5Mb. Use it all the time for AWS lambdas.
Another option to slim down containers besides using Alpine is using Buildah to build an image from scratch.
The better solution is to build containers without all of that bloat in the first place. I did up a post on that subject a little while ago.
Agree!
You link to https://lemmy.srcfiles.zip/post/3841 which does not seem to have anything to do with containers, but is about townscaping
I was wrong on the internet; apparently with certain Lemmy apps this directs to a completely different website.
~~What crack are you smoking? It's literally a post about "building lightweight hardened containers"?~~
~~Edit: wtf is townscaping? Is that like manscaping for a whole town? Or is it just regular landscaping.~~
Suuuper weird, when I click the link from the browser, I get to the correct page, but not in the Connect App. Then it's some blog about old houses and nice places in towns
Ok, that is weird and I retract my criticism. Just because I don't see it doesn't mean something unusual isn't happening there!
view more: next ›