5 ms·
Minimus container images are now free
- qwer123vbtf 3mo agonoice!
- morellonet 3mo agoJohn here (CTO and Co-Founder)… we’d be happy to answer any questions anyone has!
- ftchd 3mo agoJust a little bit of feedback: some items on the main page are duplicated, which could be confusing. For example, "nginx-advanced" appears as updated both 3 days ago and 2 hours ago.
- morellonet 3mo agoOne of those is the image, one is a Helm chart using that image. The chart has an label and icon for chart but obviously we need to make this clearer :) Thanks for the feedback!
- miyuru 3mo agoAny plans to add IPv6 support? NAT GW are costly and docker hub has full support. currently reg.mini.dev does not have AAAA records. Did not check the blob storage endpoints.
- morellonet 3mo agoCertainly something we can add, just not something any customers have wanted thus far. reg.mini.dev is really a front end to Google Artifact Registry which already supports v6. I opened an issue for our devops team to enable it for us. Thanks for the feedback!
- BIGFOOT_EXISTS 3mo agoIs there a single upstream that all images are based on? Debian? Arch? Alpine? Curious how this plays into customizing images with creator, are you guys responsible for all the packaging? Would my keester be on the line if say an upstream package got hit with an attack but I use it through creator?
- morellonet 3mo ago1. Distroless base. Imagine an effectively empty filesystem that only includes the components needed to run the app. The package manager we use is apk from Alpine and we make our full package universe of >10,000 packages available freely to Community Edition users. If you want a more 'normal' experience with a shell and apk, use the -dev versions of images that are still minimalistic but include a little more tooling like this. 2. For creator, you're basically taking any image from our public gallery and able to add whatever other packages from our universe to it, set env vars, upload files (customers typically use this for adding conf files and certificates). Then we maintain that image 'recipe' for you continuously, under the same SLAs we do all the public images. More details at https://docs.minimus.io/enterprise-edition/image-creator#image-creator https://docs.minimus.io/enterprise-edition/image-creator#ima... 3. Nope :) We are building every package across our universe continuously. Whenever there's a new version of any of them, we pull source, build package, compute what images (including creator ones) use that package, rebuild those images, test, sign.
- _def 3mo agoWhat can you say about long-term plans? The bitnami situation burned a lot of people I think, and yes we can cache your images, but switching providers still does not come for free.
- morellonet 3mo agoWe did this because we believe this market is becoming more about the integration and enterprise capabilities rather than just selling the images. The more people know about, use, and benefit from the images the more potential Enterprise Edition customers we can help.
- stusmall 3mo agoThank y'all so much for doing this. I really appreciate y'all not putting STIG/FIPS behind the paywall. Rare and aggressive move.
- briansioscl 3mo agoHello John, happy to hear that the image is free to the community, what a great contribution. May I know what is the underlying method to build the distroless image? Chainguard recently delete most of the cloud native application in their community repository, and I'm figuring how to get away from wolfi melange and apko. My closest bet is nix pkgs, but it would be great if you can share what you are using in Minimus :)
- hobofan 3mo agoAsking the very obvious question (as it's not apparent from the website): Why would I use this over DHI (Docker Hardened Images) or Chainguard Images, both of which also have a set of free hardened images?
- phishin 3mo agoAgreed. Also on front page the nginx container is 6 days old, so no daily builds
- morellonet 3mo agoWe build anytime any component within an image has a new upstream version. If there’s no new upstream versions, no reason to build. Check out the changelog tab in each image listing and you can see exactly when and why we build each time
- morellonet 3mo ago1. These are all >1200 of our images, including FIPS, and all versions… others gate many of their images 2. These are all built continuously from upstream source on a distroless base… this makes a significant difference in attack surface and CVE count re DHI images and you can easily check our word with a few scans 3. These are truly free… no auth wall, no signup, no trial, no limit on numbers of images or pulls or anything like that 4. We have really invested in making these agent ready… we have a CLI (minicli) designed for both humans and agents to easily discover, understand, migrate to, and build on them… for example, check out the AI migration prompts we provide for each image, we’ve refined these across many customer deployments such that you can copy paste into your agent of choice, point it at a Dockerfile and have it do all / nearly all the work to move to these images
- ramon156 3mo agoThe question was "why over DHI?" 1 and 2 are not a reason 3. no X, no Y, also not a reason 4. `rg agents`. Right
- figassis 3mo agoThe free tiers always go away, after they're deep in our infra. I would prefer to price it from the start.
- morellonet 3mo agoWe would be happy to sell it to you today! :) This is our new Community Edition, which are all the exact same images as the Enterprise Edition product customers around the world already use, just without all the other features like image creator, self hosting, integrations, SSO, etc. Click the discover Enterprise Edition button on lower left and you can see a quick comparison table or go to minimus.io to see all the details. EE also includes contractually backed CVE remediation and support SLAs. If you’d like to try EE and get pricing details, we’d be happy to help! Just click the button on the lower left to get started.
- zufallsheld 3mo agoWhere are these built? Can I see the Dockerfiles? How are they licensed? I get that they are free as in beer, but not libre/FLOSS?
- morellonet 3mo agoCurrently, yes free as in beer. We build every component directly from source in a SLSA 3 environment we run (mostly in GCP). Making the Dockerfiles available is a fair question, not something we’ve done thus far because it’s not particularly useful if you don’t have all the infrastructure building the components. Do you have particular scenarios you’d like the Dockerfiles for or is it just for transparency/ trust (which is a totally valid reason of course)?
- zufallsheld 3mo ago> Do you have particular scenarios you’d like the Dockerfiles for or is it just for transparency/ trust (which is a totally valid reason of course)? The latter. You or an attacker could tamper with the images - however even with the Dockerfiles I can't be sure that the provided images are built from the Dockerfiles, so in the end I'd have to trust you anyway. Also I'd be curious how you build the images. Thanks for your answer!
- morellonet 3mo agoTotally get it… practically if you don’t want to have to deal with constantly updating images you have to have some degree of trust in whomever you get them from… that said, we try to be as transparent as possible with a cryptographically verifiable SBOM for every build of every image, signing every image, providing detailed compliance test results for FIPS, STIG, CIS (see the compliance tab on each image listing) Your feedback about Dockerfiles is good though and probably something we can easily add to image listings. I opened an issue for us to add. Note that we also make our package manager freely available in Community Edition as well, which can make the Dockerfile availability more useful.
- danudey 3mo ago
- crabique 3mo agoIs their ingress-nginx-controller image similar to that of Chainguard: a drop-in replacement with the CVEs fixed?
- greggsy 3mo agoI see this is a packaging service with greater traceability and velocity than the rando images on docker hub. I believe that they will always supply the bleeding edge stable release, but it will always be your responsibility to monitor and manage issues like CVEs, rather than expecting them to do it for you.
- crabique 3mo agoThis particular image is a bit different though. By CVEs I mean the architectural stuff that was discovered after the original ingress-nginx repo was archived, so there is no "official" mitigation and it's not just a matter of bumping dependencies, the fixes are actual code. Chainguard forked the repo and is maintaining their own distribution now, but it's not free.
- stamod1 3mo agoyes it is
- cedws 3mo agoSince we started paying for Chainguard I’ve become super sold on the benefits of minimal and continually patched images. It’s just a shame that the open source community only gets to benefit from the limited free library DHI and Chainguard offer. I understand it costs money though and that needs to come from somewhere.
- morellonet 3mo agoThis is exactly why we’ve made Community Edition free. The value of hardened, well maintained images to the world writ large is huge. We believe there is sufficient value to enterprises in the SLAs and broader feature set to build a great business while making the core benefit available to everyone without friction.
- charukiewicz 3mo agoCompletely blocking the image information page to mobile user agents is completely unnecessary. I'd much rather look at your non optimized page than be told to come back on desktop. Moreover, even after switching to desktop mode on my phone, there's nothing I see that precludes you from employing a little bit of CSS to make those pages render more nicely on mobile screens.
- jjice 3mo agoSeriously. I get the sibling comment seemingly from someone involved talking about eng resources being tight, but blocking it instead of just showing a desktop page feels absurd.
- nikanj 3mo agoTakes more eng resources to block mobile than not
- morellonet 3mo agoFair complaint. As with all software development we make tradeoffs to try to balance time and capability. I’ll make sure our front end lead see this though :)
- philipbjorge 3mo agoI’ll second this, I had to send this message… > based on our discussions so far, I think we’d only need... Which they appear to have but I can't dig in on mobile.
- x______________ 3mo ago> This page is currently not available for mobile devices. For the best experience, please visit us from your computer. For what it's worth: my mobile device is a computer.
- projektfu 3mo agoTurning on "Desktop Site" on Firefox Android lets me through. Not that I disagree, just a workaround.
- tamimio 3mo agoI have no idea what the heck is this, maybe it’s a great product but a very poor website in telling what I am getting into, is this better than the usual containers? How? Supported platforms? Can I run it on arm? The usuals
- assafShapira 3mo agoyes all the images have ARM64 versions as well as x86_64
- morellonet 3mo agoIt’s a library of near 0 CVE images available to use for free. Think Docker Hub, just without vulnerabilities. They’re all normal, OCI compliant images. You can pull them, run them, and build on them like you would any other image. arm64 and amd64 builds for everything
- alfanick 3mo ago> just without vulnerabilities You surely mean "without known and reported vulnerabilities". I doubt you're proactively fixing the world across thousands of software packages /s
- morellonet 3mo agoCorrect, we are not claiming to be auditing the source of every software package in the world. The value we provide is a minimalistic architecture so you start with a significantly smaller attack surface and continuous builds of upstream so you stay at a near 0 CVE state without the substantial work required to do so yourself. Basically, we help you get all the upstream fixes from across the OSS ecosystem as quickly, safely, and easily as possible.
- sara_halper 3mo agoMinimus images support both amd64 and arm64. When you run the docker pull command, it will automatically pull the correct architecture for your system. You can also review the different SBOMs for the amd64 and arm64 images, for example - https://images.minimus.io/gallery/images/python-fips/lines/3.14/versions/3.14.6/sbom https://images.minimus.io/gallery/images/python-fips/lines/3...
- Flingerthing 3mo ago[dead]
- concerned_ctzn 3mo agogood job!
- alfanick 3mo agoI truly don't get this. What is the security policy here? Why should I trust images built by minimus.io? How do I know they don't contain malicious software? What's the point?
- morellonet 3mo agoWe build all these images directly from upstream source across thousands of projects and assemble them into standard OCI images for you. We do this continuously, every time there are new versions released upstream. The point is that you can just use these images instead of what you already have and reduce your vulnerabilities by 97%+ on average. Think Docker Hub, just without the vulnerabilities.
- alfanick 3mo agoPinky promise? How do you prove that what I download from you is actually what you promise you've build (and that SBOM is right)? Is this certified with some digital signature? From my threat attack model, you're just yet another liability - one single service to hack all your "safe" images.
- morellonet 3mo agoSure, but you could make the same argument for literally any software that you're getting that was built by someone else and have not personally inspected each line of source in. For example, you could make the same argument about RHEL or any image on Docker Hub or literally anything you're not building yourself. Respect your viewpoint and if these images aren't for you, that's totally fine of course. Many others find it useful to have someone else doing the commoditized but hard work of building thousands of components from source continuously, assembling them into ready to run images, signing, and being as open as possible about their state and configuration as possible.
- tuananh 3mo agothis space is too crowded now. everyone is copying whatever Chainguard is doing - Chainguard Images - Chainguard Libraries - Chainguard VM ...
- cedws 3mo agoBecause Chainguard cost an arm and a leg.
- morellonet 3mo agoFree markets work :) With Minimus Community Edition, you now have access to 1,000s of built from source, near 0 CVE images without cost or friction
- 2OEH8eoCRo0 3mo agoSupply chain attack waiting to happen
- alfanick 3mo agoMaybe it's their business model? Sell to bunch of people and hook them in, then "get hacked", whoops sorry. Edit: honestly I'm flagging this post. This really looks like fishing for customers to make them vulnerable in future.
- cedws 3mo agoWhat are you even talking about?
- morellonet 3mo agoNot sure what you mean here. We have many enterprise customers, in industries including government, health care, financial services around the world. The whole value of the product is helping them avoid all the risk and work associated with poorly maintained container images. We publish a full SBOM for every image so you can see exactly what's inside of it. We've worked across the industry and OSS communities to enable scanning support as well, so you can easily use whatever scanning tools you currently use (e.g. Wiz, AWS Inspector, Grype, etc) to check our images.
- csnoob 3mo agoHow can we trust the image if we don't know what is inside? An sbom says what packages are installed but what is in the packages? Alpine/debian packages show you the code that compiles the package from source, do you have that as well?
- kitd 3mo agoHow? If this, then so is DHI.
- biimugan 3mo agoWhat's the availability story? Docker Hub has pretty severe rate-limiting even if you're not an anonymous user.
- morellonet 3mo agoNo rate limiting or degradation of service for Community Edition. Same images, same registry as Enterprise Edition.
- NoNameProvided 3mo agoIn the risk reduction tab, it should compare the vulnerability count against the node-slim image. In my eyes, it takes away from the offering when they try to prop up the vuln count for the official images, and nobody deploys `node:latest`.
- itintheory 3mo ago> nobody deploys `node:latest` Oh how I wish that were true.
- morellonet 3mo agoEven the :latest is something of a wish :) You may / may not be surprised how many enterprises still run long ago EOL'd versions of various stacks, frequently on full blown OS base layers of similar vintage
- indigodaddy 3mo agoI'm interested in using these images on exe.dev. exe supports any oci images and stands it up as a microvm, in which it would be used non-ephemerally from that point. I'm assuming the images don't have any rc/services. How hard would it be to pull that back in after image deployment? (Also looks like I'd want to use the -dev images which include shell/apk, etc)
- morellonet 3mo agoCorrect they do not have any rc I’m not personally familiar with exe.dev but if it can run normal OCI images it should be pretty simple to use ours. If you want a shell and package manager and some common busybox applets, -dev variants are the best option.
- euph0ria 3mo agoThank you for this! Super valuable for contribution to all businesses. Suppose I want to add a custom PHP extension such as NewRelic, how would I go about adding that on your distroless images?
- morellonet 3mo agoDepends on your preferences but probably easiest approach is to take the -dev version of our PHP image and run a build from that to add whatever you need on top of that hardened base. You can even do a multi step build if you want to use the fully minimalistic image at runtime. Details at https://docs.minimus.io/foundations/going-distroless https://docs.minimus.io/foundations/going-distroless
- csnoob 3mo agoIs the cli open source? What about the images themselves? An easy comparison is wolfi, which is completely open source.
- rustyturtle 3mo agoused bitnami images and charts that depended on them, then they pulled them back after being bought by broadcom causing headaches. not getting bit by the rugpull again sorry.