18 ms·

MinIO stops distributing free Docker images

• deleted 11mo ago
  [deleted]
• jeroenhd 11mo ago
  Looking at the change to the README last week[1], it looks like MinIO went from "MinIO has no planned or scheduled releases for this repository" and " While a new release may be cut at any time, there is no timeline for when a subsequent release may occur." to "The MinIO community edition is now distributed as source code only". Based on promises alone, I think that means they un-dropped the open source project but still only distribute the binaries to their customers. [1]: https://github.com/minio/minio/commit/9e49d5e7a648f00e26f2246f4dc28e6b07f8c84a#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5 https://github.com/minio/minio/commit/9e49d5e7a648f00e26f224...
• weinzierl 11mo ago
  Not a full replacement but there is Garage, which was quite well received in other HN threads. https://git.deuxfleurs.fr/Deuxfleurs/garage https://git.deuxfleurs.fr/Deuxfleurs/garage
  • c0balt 11mo ago
    Can vouch for it as an adequate self-hostable option. It has some missing features, compared to Minio, and is less compatible but works for most applications.
    • olivermuty 11mo ago
      could you elaborate on this? we're looking at moving off cloudflare r2 in the somewhat near future and garage is on our short-list
      • c0balt 11mo ago
        Garage worked for most of my use-cases but it lacks, among other endpoints[0], bucket ACLs and bucket replication. Anonymous access is also an open issue[1]. They are also a comparatively young project and while fully OSS do not, afaik, appear to have a solid long term funding source yet. Though that might be an opportunity to support them, if your company is interested in picking them. [0]: https://garagehq.deuxfleurs.fr/documentation/reference-manual/s3-compatibility/ https://garagehq.deuxfleurs.fr/documentation/reference-manua... [1]: https://git.deuxfleurs.fr/Deuxfleurs/garage/issues/263 https://git.deuxfleurs.fr/Deuxfleurs/garage/issues/263
        • zenmac 11mo ago
          We are also looking into Garage, does it support 206 partial content seeking on the files in the bucket via it's http interface?
          • angst 11mo ago
            Garage should support partial content seeking via its HTTP interface, if it is S3 API compatible which includes support for range requests/206 Partial Content response.
  • Eikon 11mo ago
    Doesn't support if-match.
  • znpy 11mo ago
    Afaik Ceph has its own object-storage functionality as well, which seems to be S3-compatible: https://docs.ceph.com/en/latest/radosgw/#object-gateway https://docs.ceph.com/en/latest/radosgw/#object-gateway
    • maxloh 11mo ago
      Yeah. They also created a open source test suite for S3 clones. This is a set of unofficial Amazon AWS S3 compatibility tests, that can be useful to people implementing software that exposes an S3-like API. The tests use the Boto2 and Boto3 libraries. https://github.com/ceph/s3-tests https://github.com/ceph/s3-tests
      • yencabulator 11mo ago
        Oh heh, a trip down the memory lane. I wrote the initial version of that, in an era where AWS docs did not match observed S3 behavior. The only way to make an S3-compatible API was to create a suite of over-the-network tests to run against both AWS S3 and radosgw. We also had a little grammar-based fuzzer for S3 requests (really, any HTTP), but over the last 10+ years I've lost track of what happened to that code. That found some incompatibilities with allowed character sets etc too.
    • a10c 11mo ago
      I believe you're forced to have your data backed by a Ceph OSD. Whereas Minio can point to an NFS share on a NAS.
      • znpy 11mo ago
        > I believe you're forced to have your data backed by a Ceph OSD. It makes perfect sense as this is a feature of Ceph. > Whereas Minio can point to an NFS share on a NAS. Eh, different trade-offs.
      • dpedu 11mo ago
        Minio used to be able to do this, but they dropped this feature - "gateway mode" - several years ago.
  • Aeolun 11mo ago
    I find garage to require quite a lot of fiddling.
    • crabique 11mo ago
      Care to elaborate?
      • Aeolun 11mo ago
        There were setup commands I needed to run before the docker image did anything. I’m used to just specifying an access/secret key and having it work.
  • Kevinmetaba 11mo ago
    Garage uses the AGPL v3.0 license, which is not an open source-friendly license.
• nik736 11mo ago
  Is there a fork already?
  • stanac 11mo ago
    Do we need a fork? As an example, ffmpeg is source only for mac and windows, which just means someone else is building and distributing binaries.
    • nik736 11mo ago
      They changed their license to AGPL, removed features (Web UI, etc.) and now they don't provide docker images/binaries. It's their project but; what's next?
      • rustc 11mo ago
        > what's next? Removing existing Docker images? Seems unlikely.
        • silverwind 11mo ago
          It seems crazy that docker hub images are not immutable. Makes them really unreliable.
      • lyu07282 11mo ago
        Obviously they will eventually no longer license AGPL at all. It's wild to me how this can be a surprise to anyone, this entire company has been one gigantic red flag for years and that's just what's publicly known. It's a legal department with a software product as a side business.
  • deleted 11mo ago
    [deleted]
  • debugnik 11mo ago
    What for? The code hasn't changed, it's AGPL-3.0. They just don't release their own binaries or docker images anymore.
• the_mitsuhiko 11mo ago
  MinIO was already before tricky because their interpretation of the AGPL is way to broad.
  • stanac 11mo ago
    Do you have a link? I want to read more about that. Did they interpret any use as deriving from minio?
    • the_mitsuhiko 11mo ago
      They changed their public guidance at this point, but you can still find references to their approach to AGPL quoted here: https://news.ycombinator.com/item?id=35328316 https://news.ycombinator.com/item?id=35328316 > "When MinIO is linked to a larger software stack in any form, including statically, dynamically, pipes, or containerized and invoked remotely, the AGPL v3 applies to your use. What triggers the AGPL v3 obligations is the exchanging data between the larger stack and MinIO."
      • dns_snek 11mo ago
        Archive link: https://web.archive.org/web/20230327211209/https://min.io/compliance https://web.archive.org/web/20230327211209/https://min.io/co...
      • Tepix 11mo ago
        Yes, the page at https://www.min.io/opensource https://www.min.io/opensource no longer contains this phrase. It sounds reasonable now. I guess they talked to a lawyer.
      • fukka42 11mo ago
        Did they ever get permissions from their contributors to switch to AGPL? Last I checked they did not. They didn't require a CLA either. So no matter what they claim large parts of the codebase are still apache2.
        • 11mo ago
• MuteXR 11mo ago
  Keep in mind this is the same project that removed all useful functionality from the included web UI in the community edition with the excuse that it was too much effort to maintain. This is another case of VC-funded companies pulling up the ladder behind themselves.
  • jinkylist 11mo ago
    Is it an excuse? Maintaining code costs money, and the previous versions are provided under the license, and you're free to modify it, pull selective patches and maintain them yourself. While It'd be convenient if the license was a promise to develop and maintain features for free in perpetuity, it just isn't. I run into this in non-company backed open source projects all the time too. Some maintainer gets burned out or non-interested and all they're rewarded is people with pitchforks because they thought there were some sort of obligations to provide free updates and suppport
    • fukka42 11mo ago
      [dead]
    • ukd1 11mo ago
      It's different as a) they did offer it for free and b) have to maintain it for the closed version. However, this is also a classic move, so shouldn't be unexpected behavior these days...
    • aforwardslash 11mo ago
      It is sort of an excuse. I don't use MinIO precisely because of this kind of behaviour - if I cannot easily develop, configure and test our applications, I'm not adopting it commercially, specially when there are a ton of options to choose from. In the end, this hurts the MinIO's enterprise offering. Having a robust, easy to deploy community edition, with predictable features, is a great way of allowing integrators to develop and test using your product, and to help the product to gain traction.
    • mpalmer 11mo ago
      Conversely, if instead of making your users happy to pay you, you've made them happy to use your stuff for free, you own the consequences when you stop giving that stuff away. Welcome to HN BTW, I see you were inspired to sign up and defend the project owner.
• abujazar 11mo ago
  Time to switch to Garage for dev environments and reconsider minio for prod. This is not how to do open source.
• c0balt 11mo ago
  I'm glad to have migrated to garage in time. This is quite unfortunate though as a lot of open source projects, like plane.so, used minio via container images for s3 with docker compose.
  • Imustaskforhelp 11mo ago
    thoughts on https://github.com/coollabsio/minio https://github.com/coollabsio/minio ? I feel like this could be used till the time plane.so or other projects feel like they could migrate to garage or maybe just use these coollabsio minio docker image?
    • c0balt 11mo ago
      My problem was mostly that MinIO was not significantly better for my use-case then garage after the admin console was yanked. Thank you for the pointer though, I will take a look at this for my plane.so instance (using a private containerized minio there still).
  • mlrtime 11mo ago
    What did you lose exactly, I don't get it.
    • c0balt 11mo ago
      Minions has taken away the admin UI for everything except a bucket browser in one of the last releases. And now they have stopped publishing updates to their community edition docker images. As the linked GitHub issue points out this now means at least one vulnerability will be unpatched (unless you install from source or switch the image) for anyone relying on updates to the original container image. My loss exactly was that minio lost most of its appeal when it stopped having an integrated management console. It also seemed they were moving into a direction where features were gonna be more separated off for their aistore products over the community edition (a fair move but not something I want to happen to my deployment).
• Tepix 11mo ago
  It's an Open Source project - I don't understand what people are complaining about. Noone is entitled to receive free Docker images. I'm sure if there is enough demand, someone else who is trustworthy will step up and automate building them. What I'd like to complain about instead is the pricing page on the Min.io webpage - it doesn't list any pricing. Looking at https://cloudian.com/blog/minios-ui-removal-leaves-organizations-searching-for-alternatives/ https://cloudian.com/blog/minios-ui-removal-leaves-organizat... it seems the prices are not cheap at all (minimum of $96,000 per year). Note that Cloudian is a competitor offering a closed-source product.
  • Timshel 11mo ago
    Well removing any distribution after a CVE is a nice touch ...
  • weli 11mo ago
    When you always published and built Docker images for the public you are creating an expectation, people will rely on that and will chose your software based on that expectation. You suddenly deciding that you won't be offering updated Docker images especially after a CVE and with no prior notice (except a hidden commit 4 days ago that updated the README) is approaching malicious-level actions. If they truly cared about their community and still wanted to go through the decision of not offering public docker builds the responsible thing to do is offer a warning period, start adding notices in the repo (gh and docker) and create an easy migration path, even endorse or help some community members who would be fine with taking care of the public builds of the image. But no, they introduced the change, made no public statement about it, waited for someone to notice this, offered no explanation and went silent. After a huge CVE. Irresponsible.
    • blueflow 11mo ago
      > you are creating an expectation thats entitlement but seen from the other side.
    • phatfish 11mo ago
      This only inconveniences open source freeloaders. Maybe you can volunteer some time to build Docker images?
• jinkylist 11mo ago
  While not notifying of the change earlier is annoying, I also don't see anywhere stated that they're obligated to provide services in addition to just providing me the source. Moreover the build-instructions don't seem complicated at all, anyone already extracting value from this should be capable of pulling the source and keep on running with it.
• some-ai-dev 11mo ago
  I wonder how many people only use Minio as a localdev S3 alternative. At least that's all we use it for really
  • grishka 11mo ago
    I use it to test my tiny written-from-scratch S3 client in my server app. But then I already have it installed, it already works, and I don't care about updates.
  • stuaxo 11mo ago
    That's how I use it. It seems to also provide a lot of other stuff I don't use.
  • luke5441 11mo ago
    Every time I used it for more than that I ran into performance and other concerns (like durability and consistency) pretty quickly. I cannot imagine how this is used seriously when there is something like Ceph available. Turns out most file systems are horrible key-value stores.
    • jinkylist 11mo ago
      >I cannot imagine how this is used seriously when there is something like Ceph available. Adopting Ceph is adopting a Ceph engineer, any use-case with the need and funding to run Ceph on production would easily be able to pay for commercial licenses and/or contribute majorly to this or their own fork. They work in different ball-parks entirely
  • rglullis 11mo ago
    I have a 160TB minio cluster running for 4+ years who had dealt beautifully with node outages, one drive failure and the occassional hiccups on the datacenter. I was okay with not having support because I am not part of their customer base. I was okay with not having the webUI, though I wish they made an option where the webUI would be available for some basic-tier paid customers. But I can not be okay with this move. They are just giving the finger to all the community. They never tried to work out a solution that could let smaller users to contribute or support. I will seriously have to consider moving to Hetzner object storage.
• huflungdung 11mo ago
  [dead]
• deleted 11mo ago
  [deleted]
• imiric 11mo ago
  Shame. Textbook OSS rug pull. These people love to rely on OSS, and claim how committed they are to contribute to the ecosystem and to their community, but as soon as people are drawn to the project, start relying on it and using it in the same spirit of OSS that they enjoy themselves (which their chosen license allows, mind you), then it becomes a financial burden, priorities shift to their commercial offering, there's no "bandwidth" to maintain and support the "community" edition, and so on. STOP ABUSING OSS AS A MARKETING GIMMICK. Or perhaps an advice to people who might actually listen: stop being attracted to open source projects because of the word "open", and because you can use it gratis. There are plenty of good proprietary and commercial software whose authors treat their users with more respect than these leeches of good will and abusers of trust. I'm not against OSS being commercialized. In fact, I think that it's crucial for maintaining a healthy project in the long-term[1][2]. But this lingers on the developer having respect and equal regard for all their users, regardless of how much they're paying them. Yes, nobody working on software should be expected to work for free. But there is a philosophy behind this movement that goes beyond a financial transaction. It only works if everyone in the ecosystem is honest, and first and foremost has the intention of making the world a better place for everyone, by not only depending on others who have this mindset, but by adopting it themselves. Claiming to be part of the OSS community, but being hostile to your OSS users is dishonest at best, and worthy of all criticism. [1]: https://news.ycombinator.com/item?id=45540307 https://news.ycombinator.com/item?id=45540307 [2]: https://news.ycombinator.com/item?id=45537750 https://news.ycombinator.com/item?id=45537750
  • muragekibicho 11mo ago
    Isn't your diatribe contradictory. Your last paragraph appears to contradict your 'beliefs'.
  • jinkylist 11mo ago
    >It only works if everyone in the ecosystem is honest In general, applying this to anything with the general public, I don't expect it to work. This is why we have laws, licenses and rules in the first place. You can preach all you want but it won't change humanity, you need something concrete, something written and agreed, like a license. Not all licenses protect the freedoms and rights you're used to in other licenses, and it needs to be taken into account when adopting any project. License terms that don't guarantee any sort of support or updates when you need them aren't in consideration at that point.
• tom1337 11mo ago
  I am also so confused as to what MinIO is now. All I see on the website is AIStor - have they dropped the "S3 Alternative" Marketing and went full AI?
  • deleted 11mo ago
    [deleted]
  • antiloper 11mo ago
    If you want VC funding, your marketing pages need to go all-in on AI. Even if your product has nothing to do with it.
    • timcobb 11mo ago
      Yikes
    • egorfine 11mo ago
      Unfortunately yes. I have been looking at one of the well-known VPN infrastructure providers and they use "AI" on their website a bazillion times. Insane.
• aranw 11mo ago
  Recently adopted the Go MinIO SDK to abstract cloud-specific APIs. Really hoping the SDKs don't get a licensing change or yanked next
  • arccy 11mo ago
    there's still gocloud.dev/blob ...
• adamcharnock 11mo ago
  We're working on a binary build process now. We hope to have something up at https://github.com/golithus https://github.com/golithus soon. We use MinIO (community edition) a fair amount. And while we like it, it is also becoming increasingly clear that our days of deploying are numbered. We want to start experimenting with Garage for smaller deployments, and would be interesting to hear of any production experiences there. (Anyone done multi-PiB deployments?) Other than that we're going to start looking at Ceph/Rook for larger deployments.
  • xavxav 11mo ago
    garage devs have told me of 10PiB+ deployments in production, but I've never operated one at that scale so I can't share much insight into the experience. Probably best to ask on their matrix chat.
  • adamcharnock 11mo ago
    Done: https://github.com/golithus/minio-builds https://github.com/golithus/minio-builds
• PlkMarudny 11mo ago
  [dead]
• vietvu 11mo ago
  It's ok, just don't use them anymore if you don't like it. I will switch to something else.
• djdjsjejb 11mo ago
  this sucks because now im forced to make seaweedfs and ceph work haha seriously, minio sucks perf wise but they really did a good job making it easy to deploy with docker
• jraph 11mo ago
  The title of the HN submission might look a bit misleading. It's easy to misinterpret it and think MinIO stops being open source (which would be a bigger deal IMHO). I think this would be better: "MinIO stops distributing free Docker images" --- See also the relevant README section: https://github.com/minio/minio?tab=readme-ov-file#source-only-distribution https://github.com/minio/minio?tab=readme-ov-file#source-onl...
  • 8-prime 11mo ago
    That was my interpretation of the title when I first clicked it. Still interesting but easy to misunderstand nevertheless.
  • tomhow 11mo ago
    OK, we updated the title to your suggested one now.
    • goku12 11mo ago
      What was the previous title?
      • jraph 11mo ago
        It was: MinIO (apparently) becomes source-only Thanks tomhow!
  • munchlax 11mo ago
    For those left wondering what the original title was, it said minio went source-only. I don't see the problem in either case. For a Gentoo user, it changes nothing.
• ezascanbe 11mo ago
  Full disclosure: I work for Cloudian. While I understand the frustration with MinIO’s approach here, I want to be upfront about what Cloudian HyperStore is and isn’t - it is designed for multi-node, multi-site deployments (think 3+ nodes minimum) and performs best on bare metal or dedicated infrastructure rather than containerized environments. It’s a very mature S3 and offers IAM, SQS and STS endpoints as well. If you’re running MinIO at scale in production and looking at migration options, I’m happy to connect you with our team who can discuss whether HyperStore makes sense for your use case. That said, for single-node dev environments or lightweight deployments that many here are using MinIO for, the community alternatives mentioned in this thread are probably better fits. Different tools for different scales. Happy to answer any technical questions about HyperStore’s architecture if helpful.
  • killingtime74 11mo ago
    What is Cloudian? You guys didn't develop Minio did you? (Google says Minio Inc?) If you did it's hard to tell.
    • ezascanbe 11mo ago
      No, Cloudian did not develop MinIO - completely separate companies. MinIO was developed by MinIO Inc. Cloudian makes HyperStore, which is our own S3-compatible object storage solution. We’re a competitor to MinIO, not affiliated with them in any way.
      • killingtime74 11mo ago
        Ah I see. Will check yours out.
  • blitzar 11mo ago
    #ad
• Imustaskforhelp 11mo ago
  https://github.com/coollabsio/minio https://github.com/coollabsio/minio I was reading the github discussion and found out that coollabs has taken on the decision to make docker images for these. https://github.com/coollabsio/minio https://github.com/coollabsio/minio https://github.com/minio/minio/issues/21647#issuecomment-3429334402 https://github.com/minio/minio/issues/21647#issuecomment-342... >Until we (the community) figure out something, I made an automated docker image version here: https://github.com/coollabsio/minio https://github.com/coollabsio/minio The latest release is already available on ghcr and on dockerhub for amd and arm. Well they have locked the discussion right now it seems but hope the community does something since my brother once asked for how to store audio and I thought that something like S3 could be perfect for it and wanted him to use minio or check it out. Idk what I will recommend now? Garage? Seaweedfs?
  • mlrtime 11mo ago
    Wow, ~75 lines of Dockerfile and ~300 lines of github actions, hosted on a FREE platform. Seriously, what is the rage here, anyone could do this.
    • ThatPlayer 11mo ago
      Anyone including MinIO. So why did they stop doing it when it was so easy? Especially because they haven't provided any reasoning for this decision, so everyone assumes the worst. I can't really think of any reason for this that puts them in a positive light either, can you?
    • Imustaskforhelp 11mo ago
      I hope you have read the github issue page This was the first person after so so many comments to actually do something about it, and he's from coolify which can be decently trusted with. Everybody likes to rant and the dislikes on github issues show but I just respect the guy for even taking his time to write this. Sure you can try to reduce it to LOC or anyone can do this, but did you? Also there is a trust factor, I can trust coolify's docker image as compared to any other people.
• woopwoop24 11mo ago
  garage and for the minio gateway (RIP) i use versitygw
  • toddnni 11mo ago
    Have been looking for minio alternative for long already. Found versitygw lately and would like to share the joy. It feels very promising. Fits to many small or lab use cases. It does not actually solve the trickiness of managing large storage but relies on the backend (that is usually fs like zfs in small setups). However, seems to be quite new project plus the risk, that the owning company takes it to bad direction, is there too. https://github.com/versity/versitygw/ https://github.com/versity/versitygw/
• computersuck 11mo ago
  Just make a fork and release built images via github actions with ghcr. Then ask people to switch to it. The great thing about open src is the ability to walk away. removed features in new release? fork and put it back. quit complaining and be the change the world needs you to be
  • Imustaskforhelp 11mo ago
    https://github.com/coollabsio/minio https://github.com/coollabsio/minio Can't emphasize on it enough but I trust the coolify team enough. Lets all jump to this ig There are people who are being the change they want to see, thanks coolify team.
  • Raed667 11mo ago
    back in the day, I had an automated Github action that would pull and build a polyfill.io image every time there was a tagged release You don't even need to fork the project, you can just extend / distribute
• antonyh 11mo ago
  I don't see the problem here in theory - if I want to trust something fully I'll build it myself in my own pipeline, often with additional hardening as needed. It only needs scripting out the build process to fit alongside my other code. I even do this for Linux apps like Signal because I want a clean binary that matches the Git tag, packaged exactly right for my system, built with the libraries already in place locally. What's not cool is not pushing a fresh Docker image to secure the CVE, leaving anyone using Docker hanging. Regardless of the new policy, they should have followed through and made the fix public on all distribution channels. Leaving a known unsafe version as the last release is irresponsible.
  • GrinningFool 11mo ago
    > Leaving a known unsafe version as the last release is irresponsible. I think they should have done a better job of announcing this ahead of time (or at all, really); but there's realistically never going to be a CVE-free release to stop on, because the next CVE is just around the corner.
    • GrinningFool 11mo ago
      I'm not sure why I got downvoted here. Minio's behavior here is shitty - but in a day or a month after the last image is released, there /will/ be a CVE that affects that image. By GPs statement, when are they then able to stop releasing?
      • jamesnorden 11mo ago
        Probably because it's a meaningless platitude like saying the only safe computers are offline ones, it doesn't address the issue at hand.
• mattbee 11mo ago
  They abandoned documentation (edit: for the open source codebase) a couple of weeks ago - that seems more significant. From their Slack on Oct 10: "The documentation sites at docs.min.io/community have been pulled of this morning and will redirect to the equivalent AIStor documentation where possible". [emphasis mine] The minio/docs repository hasn't been updated in 2 weeks now, and the implication is that isn't going to be. Even when I set up a minio cluster this February, it was both impressively easy and hard in a few small aspects. The most crucial installation tips - around 100Gb networking, Linux kernel tunables and fault-finding - were hung off comments on their github, talking about files that were deleted from the repository years ago. I've built a cluster for a client that's being expanded to ≈100PB this year. The price of support comes in at at slightly less than the equivalent amount of S3 storage (not including the actual hosting costs!). The value of it just isn't that high to my client - so I guess we're just coasting on what we can get now, and will have to see what real community might form around the source. I'm not a free software die-hard so I'm grateful for the work minio have put into the world, and the business it's enabling. But it seems super-clear they're stopping those contributions, and I'd bet the final open source release will happen in the next year. If anyone else is hosting with minio & can't afford the support either :) please drop me a line and maybe we can get something going.
  • Joker_vD 11mo ago
    Nah, it's fine. It's Open Source, you can document it yourself if you need to! But there is no obligation from the MinIO authors to provide it, you're not entitled to it.
    • MrDarcy 11mo ago
      It sounds like you’re being sarcastic but what you say is correct and true.
      • danudey 11mo ago
        It can be correct and true while at the same time being bad-faith and user-hostile.
• clan 11mo ago
  Reasonable. That seems to be the key word. One camp argues: Expect nothing. Move on. The other: Could they - with very little effort (reasonable) - have choosen a more palatable route. There must be a middle ground between the nihilists and the pampered.
• adamcharnock 11mo ago
  We [0] use MinIO with for our clients so we've just thrown together a nightly build process. Use/fork as you wish: https://github.com/golithus/minio-builds https://github.com/golithus/minio-builds Example use: docker run -p 9000:9000 -p 9001:9001 ghcr.io/golithus/minio:latest [0]: https://lithus.eu https://lithus.eu
  • xrd 11mo ago
    If anyone is wondering, the Dockerfile for this repo (thanks for sharing!) basically just copies the binary in, it is a 19 line dockerfile. I see both sides of the argument here, the people maintaining minio should not have to push docker images for free, it is work to maintain and test, especially across all the host platforms. And, this work isn't that complicated if you want to do it yourself. https://github.com/golithus/minio-builds/blob/main/Dockerfile https://github.com/golithus/minio-builds/blob/main/Dockerfil...
    • adamcharnock 11mo ago
      No problem! And it is very true. Although the binary does also need building, which is also handled in the above actions workflow.
    • colechristensen 11mo ago
      >I see both sides of the argument here, the people maintaining minio should not have to push docker images for free, it is work to maintain and test, especially across all the host platforms. And, this work isn't that complicated if you want to do it yourself I don't. It's automated, it needs approximately zero attention. This is just a company that got where it was benefitting from open source taking the free toys away thinking there'll be profit in it.
      • xrd 11mo ago
        I've spent a lot of time trying to get pytorch working inside docker against cuda. That's a big challenge even just on one architecture. It isn't as simple as you make it to be and they have to determine how they allocate resources so they can pay people. I'm still grateful for this project and would rather they dice focus on functionally than packaging.
• asgeirn 11mo ago
  Getting it from source is as easy as `go install github.com/minio/minio@latest` if you have a recent Go. In addition your favorite Linux distribution probably has it as from-source builds already. For a container image you could try making one from Alpine or Wolfi.
• kaoussi 11mo ago
  I built my own S3-less Minio alternative few weeks ago, should I open source it? It's built using Rust and React Router. Just playing around with it
• antiloper 11mo ago
  Just run `docker build` yourself. Why does this non-issue spawn dozens of comments? This isn't some impossible-to-build Windows C++ project.
• reustle 11mo ago
  Render also pushes MinIO as their recommended equivalent to S3 for their customers (using docker), similar to Bucketeer on Heroku. https://render.com/docs/deploy-minio https://render.com/docs/deploy-minio Hopefully this will finally push Render to build their own S3 wrapper.
  • anurag 11mo ago
    (Render CEO) We're prioritizing Object Storage independent of this move.
• yodon 11mo ago
  What did MinIO say to Wordpress? "hold my beer"
• deleted 11mo ago
  [deleted]
• tzahifadida 11mo ago
  This reminds me about the bitnami containers. They pulled the docker images so everyone migrated away because they fear they will also pull the artifacts building the project. They never said that. They seem to be continuing to updating the projects and providing access to the artifacts. It is very easy to build the dockers... it is just a dockerfile really... There is really no upside to stop updating the projects, it is free marketing...
• spicyusername 11mo ago
  Lots of people in this thread keep repeating the idea that, "Nobody owes anybody anything". Sure, just like nobody owes minio goodwill or business. People sour on these kinds of things because they feel sneaky and backhanded. It tells you something about the kind of people you're working with. Imagine if a food kitchen suddenly started charging for the food, without notice. Or they started charging to use changing rooms in clothing stores. Etc, etc. You'd, rightly, expect a negative reaction, even if the "food kitchen doesn't owe anybody anything". The biggest misstep in these situations is the corporations avoiding being honest and communicative about why the changes are suddenly necessary. We all know, intuitively, that in most cases its because it's not for a good reason. It's because they are greedy or otherwise feel pressured to show infinite growth.
• gethly 11mo ago
  I think Minio is the only Go client for S3 API and S3-compatible APIs. I cannot say I liked using it, but I had no choice. Nowadays I run my own file storage with my own API, so I no longer care. But if anyone wants to run their own file storage(so not a client), there is https://github.com/seaweedfs/seaweedfs https://github.com/seaweedfs/seaweedfs
  • nthdesign 11mo ago
    I've used the minio-go client library for about a year now. I don't see anything in the minio-go README or elsewhere to make me think it will no longer be supported. In fact, the most recently merged PR was yesterday. There are some other Go S3 clients, like https://github.com/kelindar/s3 https://github.com/kelindar/s3, but I don't know if any other Go S3 clients have the complete set of features that minio-go has.
  • duskwuff 11mo ago
    Surely there's github.com/aws/aws-sdk-go-v2 ?
• cduzz 11mo ago
  I haven't used minio in years, and when I did I only fiddled around with it, but my recollection of it is that it's about the simplest build chain imaginable. Install modern golang, build minio, get single binary. Anyone relying on an opensource tool like minio, needs to look at: * organization supporting it * the license * the build chain * who else uses it? * the distribution artifact needed for production. Once you've looked at that you can decide "is this an anchor I want to handcuff myself to and hope the anchor won't jump into the icy blue deep taking me and my dreams with it?" If the org behind it ever decides to rugpull/elastic you, what're you gonna do? At least with something like minio, if they're still distributing the source it's trivial to build (and if you can't build it you should evaluate if you're in a position to rely on it). Let's look at other cool open source things like SigNoz which distribute only docker artifacts (as far as I remember, anyhow) -- if they were to rugpull that people relying on it would be totally lost at sea. This isn't to say that this isn't poor behavior on minio's part, but I feel like they've been signaling us for a while that they're looking to repay their VC patrons.
  • apavlo 11mo ago
    > If the org behind it ever decides to rugpull/elastic you I love it that you use "elastic" as a verb here.
  • goku12 11mo ago
    They have also removed the web UI and stopped updating the documentation for the community edition. The former is not extremely serious as the community can easily replace it. The latter is arguably the worst among all the changes that we know of. While they do redirect community documentation towards its enterprise counterpart, it's becoming clear that the differences in the community edition won't be addressed at all. That will make MinIO community edition less viable over time. Overall, it's pretty clear that they don't view the OSS users kindly or want them around. I'm pretty sure that they would drop the entire community edition if they could do so legally and without much fuzz. You can expect more like this in the future. So this story shouldn't be seen simply as the loss of a docker image.
    • 11mo ago
• Zopieux 11mo ago
  Just use Garage. https://git.deuxfleurs.fr/Deuxfleurs/garage https://git.deuxfleurs.fr/Deuxfleurs/garage
• deleted 11mo ago
  [deleted]
• MarkHeijnekamp 11mo ago
  [dead]
• up2isomorphism 11mo ago
  Just build your damn image if you need it. They don’t owe you anything.
• serf 11mo ago
  minio is guilty of a lot worse sins than pulling a docker image -- hate them for those, not because it's more inconvenient to run.
• akagusu 11mo ago
  Item 15 of the license states: THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM *"AS IS"* WITHOUT WARRANTY OF ANY KIND They have no obligations to provide documentation, binaries or anything beyond the source code. I personally think this is a better option than migrating from an open source license to a source available and I would like more project adopt this approach from the beginning of their projects, to set people's expectation right.
  • simiones 11mo ago
    Which would be very relevant if anyone were trying to sue them for this - which no one is. The license establishes the limits of legal requirements and responsibilities. It doesn't shield you from criticisms and people being annoyed with you.
• lloydatkinson 11mo ago
  Why? The maintainer in the link chooses to be a dick and refuses to explain literally any of the weird decisions they've been making. That would at least help people understand?
• ksajadi 11mo ago
  I think both sides of this argument are correct: 1. MinIO is a business and they don't owe anything to anyone for free. 2. People using the OSS version also are free to express their dissatisfaction. This is not contract law though. This is about using OSS as a marketing gimmick to get mindshare, penetrate the market and then do a bait and switch. From one hand, it is within their right to do whatever they want as marketing. From the other hand, we as the community should be more aware of OSS as marketing vs OSS as we would like to see it. There is a damage to the community however: this erodes trust in OSS companies, so just like "content marketing" or "influencers" or any other type of marketing, after a while it loses its effectiveness, to the detriment of real "content", real "influence" and real "OSS".
  • goku12 11mo ago
    I agree with all the points you make. Just adding a detail to the following bit: > 1. MinIO is a business and they don't owe anything to anyone for free. I don't think MinIO discontinuing the free docker image is really the problem here. Creating and distributing such images cost them practically nothing - either in infrastructure costs or in HR costs. If they find it that difficult, they only need to say it. Either the community or another company will gladly take it up for free. Even other cloud projects have alternative distributions like Bitnami builds. The real issue is the pattern of behavior that this move exposes. They seem to have removed the web UI from the community edition claiming that it's hard to maintain (another thing the community would have gladly taken up if they were informed). They also stopped updating the community documentation. And these largely escaped attention until the docker build was discontinued. That itself is controversial since much effort wasn't spent in letting the users know that their current image was going to suffer bitrot indefinitely. Apparently there was also a CVE which was fixed in the source. They didn't consider it necessary to at least push the fixed container as a final measure. All these are certainly hostile and unkind towards the community and it's bordering on dishonesty. They didn't lie. But neither did they do the bare minimum expected when taking such a drastic measure. It's clear that they're withdrawing their generosity for more profits after gaining a lot of mindshare with their earlier offering. I don't believe that the docker image alone would have inflamed the community so much.
  • 11mo ago
• tonyhart7 11mo ago
  lmao they dont learn anything after redis case are they????
• elAhmo 11mo ago
  I regret recommending using at in our team. This move can’t be anything else other than malicious.
• canto 11mo ago
  It's absolutely stunning that people actually defend this behaviour! The community is having an outrage - and rightfully so - about a silently discontinued artifact delivery at a very critical time. Which is their opinion and every human being is entitled to have their own opinion and state it openly. It is also perfectly fine to expect a standardised behaviour to continue. However, what is most important is that is perfectly fine to shame an open source product for pulling features and money grabbing people after years of gathering community and locking them in.
  • atemerev 11mo ago
    I don't understand the point. The entire raison d'être of this project is that you self-host it and don't pay money for S3 and control your supply chain. If you are denied this possibility — it is much easier just to use S3.
    • Tepix 11mo ago
      Denied as in „use their supplied Dockerfile and type 'docker build'"?
  • whalesalad 11mo ago
    I don't think the people in this thread have any concept of how much $$$ it costs to distribute a free container that is going to be downloaded billions of times. You are a farmer, not a big fancy profitable one. Your tractor is from 1970 and works great, when it works. Your wife has health problems and can't really help out around the farm much - kids have gone off - so you just do things mostly by yourself. With your lucky dog Skip by your side. Even though times are tough and money ain't coming in like it used to - you still give free produce to the local schools and shelters. You've been doing it for over 20 years, and the community loves you for it. But then your wife passes. Medical bills are too high. You can't give away free produce to the local schools anymore. The community is outraged. They come to your farm with pitchforks. They set your barn and fields on fire. This is kinda what this thread feels like lol.
    • 11mo ago
• singpolyma3 11mo ago
  More projects should do this.
• didip 11mo ago
  I never understood Minio. Why not just use S3? Why not just use Ceph? If you need just the interface for dev environment, I am sure Claude can cobble it together in 1 day. This seems like a maneuver of a dying company.
• mirax 11mo ago
  A developer not offering builds themself is a common thing in package managers, like apt or pacman. I don't get why it should be any different for Docker images.
• Kevinmetaba 11mo ago
  I've been testing the RustFS product for over a month now. While there are some minor bugs, Rust is very stable. Why didn't YC invest in such a great product?
• giancarlostoro 11mo ago
  Quite a downward spiral for them. Wow. I mean I get the yearning for turning a profit, but this is yikes. This is the type of thing that guarantees most people using your open source / free variant never return.
• anacrolix 11mo ago
  Open source is sick. Everyone wants it (both to maintain a successful project, and to use them) until you maintain a popular project for a reasonable time then your realise you're getting used for fuck all value. We need a healthy way to support open source developers. This isn't working. Companies are taking advantage, and individuals are overwhelmed with choice and have delusional expectations.
  • nunez 11mo ago
    It would be cool if The Linux Foundation had a fund to support open-source devs with stuff, like a stipend or hosting costs, kind of like what exists in the hospitality space. I know that this sort-of exists, but it feels distributed amongst a few big companies and is entirely at the whims of their quarterly performance.
• kolja005 11mo ago
  What are folks doing who were just using it for CI/test/dev environments? Just build the image yourself? Use Garage as some have suggested? I'm curious what people see as the pros and cons.
• vishnukvmd 11mo ago
  It seems like they've pivoted from being a FOSS alternative to AWS S3 to whatever AIStore[1] is. [1]: https://www.min.io/product/aistor https://www.min.io/product/aistor
• jd24 11mo ago
  Surprised by the entitlement of some people. This was FREE labor they were providing, it was never going to last forever.
  • film42 11mo ago
    They created their business on open source. Free software was their top of funnel. Free customers become paid customers, and fund the business. They are more than welcome to change this, but there is no way they don't end up with egg on their face, and that's what we're seeing here.
• fithisux 11mo ago
  Imagine having to build LibreOffice from source to get it installed e.g. on Windows Not bad as long the scripts as there.
• mikey_p 11mo ago
  No need to get mad or upset about this at all, MinIO is telling us exactly who they are: They want to be a commercial software vendor, and they don't like open source. As long as they aren't advertising their product as open source, I don't see an issue.
  • deleted 11mo ago
    [deleted]
• wczekalski 11mo ago
  We moved to Seaweedfs around one year ago and I couldn't be happier. It also fixed all of the performance problems we had on MinIO.
• _nhh 11mo ago
  https://garagehq.deuxfleurs.fr/ https://garagehq.deuxfleurs.fr/
• msarrel 11mo ago
  It's sad to see a company that built itself using (and yes I purposely choose the word using) the community abandon the community in pursuit of maximal profit.
• gigatexal 11mo ago
  what a terrible turn ... screw 'em so what're you folks moving to? spinning up a local minio instance was what I always sprung for when doing local testing of s3 things... Edit: 9.4k stars. Looks compelling. https://github.com/rustfs/rustfs https://github.com/rustfs/rustfs
  • EasyMark 11mo ago
    We'll just build our own docker image, it's not a huge task
• andruby 11mo ago
  I hadn't seen the news about MinIO yet. For others that are surprised by this, it seems that there is a fork of the UI called OpenMaxIO https://github.com/OpenMaxIO/openmaxio-object-browser https://github.com/OpenMaxIO/openmaxio-object-browser
• AtNightWeCode 11mo ago
  I used MinIO for local dev. I can use S3 or R2 in some cases instead. Kinda crazy to find out that people use these Docker images in production. Why on earth would you do that?
• aakkaakk 11mo ago
  This is a clear Rugpull and Enshittification, no matter what perspective you have.
• cyberax 11mo ago
  Any recommendations for a simple S3 implementation for a local docker-compose development setup for mocking S3? Ideally with a nice UI to check/manipulate files.
• icemelt8 11mo ago
  Once again people will find out that no software should be free.
• caymanjim 11mo ago
  I don't think this is really a big deal. Plenty of others already maintain public OCI images of Minio (Bitnami is one example). So long as that's the case, there are options. I'm not familiar with Minio's licensing terms, so maybe they can put an end to that practice if they want to, but I suspect there are drop-in replacements other than the official Minio Docker Hub image. What Minio is doing wrong here is thinking too highly of themselves. Their product is a fine implementation of S3-compatible object storage. It has some features that make it attractive for selfhosting. It's far from the only solution, though. The harder they make it to use, the more people are going to switch to easier alternatives. A lot of companies try to lock down their popular open source/free products once they have a large market share. It always backfires. Hashicorp did this. There's no reason to use Terraform anymore; OpenTofu is a drop-in replacement that is just as good for almost everyone, and all the community support will shift to it such that it will inevitably be far superior to Terraform. Redis became Valkey. MySQL became MariaDB. OwnCloud became Nextcloud. There are countless examples. Yeah, the commercial entities continue to exist. For companies that need support and contracts, there will still be a market. But they are destroying their pipeline for new customers. Why would anyone use a closed commercial project with no community contribution when there's a free, open source option that's either a 100% compatible drop-in replacement or a low-effort pivot to a functionally-equivalent solution without vendor lock-in and burdensome restrictions? Minio is shooting themselves in the foot. Most people don't give a crap what's backing their object storage, so long as it works.
  • baobun 11mo ago
    > Plenty of others already maintain public OCI images of Minio (Bitnami is one example). Looks like that's coming to an end too. https://community.broadcom.com/tanzu/blogs/beltran-rueda-borrego/2025/08/18/how-to-prepare-for-the-bitnami-changes-coming-soon https://community.broadcom.com/tanzu/blogs/beltran-rueda-bor... https://news.ycombinator.com/item?id=45048419 https://news.ycombinator.com/item?id=45048419
    • caymanjim 11mo ago
      Yeah, I saw that recently. linuxserver.io bundles a lot of apps into OCI images, and I use many of theirs because they tend to be better-designed than official ones—or at least more consistent. And while some people might be intimidated by it, it's not a huge lift to make your own images. I don't mean to trivialize it, because it's at best inconvenient, and can be challenging. In many cases it's only a few minutes of work to bundle something up. LLMs are great at this. For a Golang app like Minio, it's a piece of cake, since you don't have to install a zillion dependencies manually.
• vanillax 11mo ago
  Garage for s3 emulation is a great tool. https://garagehq.deuxfleurs.fr/ https://garagehq.deuxfleurs.fr/
• ktosobcy 11mo ago
  /me waiting for all complaining about lack of docker image to step up and start providing those images ]:->
• mobileturdfctry 11mo ago
  This is interesting. I've recently been doing quite a bit of research into what my "future stack" is going to be for backend. MinIO regularly came onto my radar but one heuristic (among many) I use to determine which software is TRULY open source and which is far less likely to remain open source is whether they even provide a link to their Github page and prominently display it on their website. MinIO was triggering my "not really open source" radar for this reason. I'm still dabbling but have kind of latched onto the idea of using Ceph. To my understanding they were acquired by RedHat, and the project has all the signs of real open source, including the fact that it originated as a doctoral research project at the University of California, Santa Cruz, with initial funding from the U.S. Department of Energy.
• digikata 11mo ago
  Incidentally there is a open source S3 project in rust that I have been following. About a year ago, I applied Garage images to replace some minio instances used in CI pipelines - lighter weight and faster to come up. https://github.com/deuxfleurs-org/garage https://github.com/deuxfleurs-org/garage
• ddxv 11mo ago
  I've switched to garage and it's been absolutely fantastic. I don't know if it has a UI yet, but it's been rock solid.
• mikedonovan1987 11mo ago
  Hey Mike Donovan here. I work at Docker and help with the Docker Official Image (DOI) program. If you're interested in a DOI being created to support the MinIO community chime in here: https://github.com/minio/minio/discussions/21655 https://github.com/minio/minio/discussions/21655
• deleted 11mo ago
  [deleted]
• dimastopel 11mo ago
  Shameless plug: try Minimus! Minimalistic and always updated container images. We have the MinIO image and it is always up to date. https://www.minimus.io/ https://www.minimus.io/
• reconnecting 11mo ago
  I thought one day in the hn TOP-5 was more than enough for MinIO. I'm even starting to wonder, should we also drop Docker builds to get the same amount of PR for our open-source project.
  • Pet_Ant 11mo ago
    Well some say 'all publicity is good publicity', I think in this case it has hurt MinIO more than anything as far as public adoption is concerned.
    • reconnecting 11mo ago
      I believe it's too early to judge public adoption. Let's see in a few years if it degrades somehow. For now, they jumped from 55,880 to 56,319 GitHub stars in one day. From the product side, I don't see how this should affect new adopters who didn't read the hn post yesterday
      • elAhmo 11mo ago
        GitHub stars are useless metric.
        • msarrel 11mo ago
          Almost as useless as docker pulls, and MinIO claims both as vanity metrics.
          • reconnecting 11mo ago
            OK, have a look at GitHub contributors metric. 404 today, 405 yesterday. Just to clarify, I'm not affiliated with or protecting MinIO, I don't know anything about this software. But it seems to me that there's some overreaction about Docker here, and in reality it is highly possible that this decision might not affect the product the way it's being discussed these days.
• chuckadams 11mo ago
  On one hand, MinIO isn't obligated to anyone... on the other hand, there's a lot of people who now feel obligated to not use MinIO anymore. Given that MinIO won't patch their container images, are obligated in many cases. A Dockerfile that actually builds instead of copying binary blobs should be as simple as one that executes `go build`. So a fork that just adds that one step seems inevitable. Seems such a waste on many levels.
• nekusar 11mo ago
  So, basically, MinIO is dead. Time to move on, folks. Dead horse is dead. Kicking it will release toxic decomposition sludge.
  • baq 11mo ago
    I built my first Slackware box from source. How times changed.
    • benterix 11mo ago
      Sad to break it to you but it was 30 years ago. We have a tendency to stick to what we know but everything changes constantly and us being connected amplifies that.
      • idkcomputers 11mo ago
        Boomers stuck behind the times, vendoring their dependencies and even looking at the code they compile. Get with the program already and just push another container!
        • hansmayer 11mo ago
          Strong "Just give me the exe, why is this published as code" vibe :)
          • reconnecting 11mo ago
            ...published as code in a printed magazine.
      • forgetfulness 11mo ago
        I imagine that this makes it much less viable for hobby use, or as a dependency for other open source projects, but setting up a private docker registry and building this image nightly isn’t onerous for any business
• akatsutki 11mo ago
  [flagged]
  • anajimi 11mo ago
    Could you elaborate please?
  • JokerDan 11mo ago
    Why is DHH being mentioned? Nothing to do with MinIO and their docker builds...
  • busterarm 11mo ago
    Take your pitchforks and your internet hate-mob somewhere else, please.
• WhyNotHugo 11mo ago
  Maintaining docker builds isn’t that huge of a burden (and likely very useful for them too), and they’re delegating hosting to a third party… I don’t get what they’re trying to achieve here.
  • ComputerGuru 11mo ago
    Money
    • snihalani 11mo ago
      this. They want to show more paid subscribers to VCs and enabling open source is eating their lunch
  • vbezhenar 11mo ago
    They're trying to force some free users to pay them for binary builds.
    • reconnecting 11mo ago
      Are they? I even checked the pricing page, and there is no mention of any builds as paid features.
      • vbezhenar 11mo ago
        https://www.min.io/download?platform=docker https://www.min.io/download?platform=docker https://docs.min.io/enterprise/aistor-object-store/installation/container/install/ https://docs.min.io/enterprise/aistor-object-store/installat... podman pull quay.io/minio/aistor/minio:latest podman run minio/aistor/minio --version So I suppose those are official binaries which require license to use.
        • reconnecting 11mo ago
          I mean, what's the difference in pricing between AGPL and a commercial license? €50k/year? €100k/year? Do you think Docker binaries are something that could hypothetically drive conversion from AGPL users to commercial licenses?
• Jeslijar 11mo ago
  I'll let docker's security team know that an insecure, obsolete docker image is being served and the maintainers have officially acknowledged they will no longer support it. Best to get insecure and vulnerable software out of the hands of those who may not be familiar with this CVE or their change in policy that has not gotten a press release in any way.
  • pelagicAustral 11mo ago
    Someone seem to already be at it on Discussions https://github.com/minio/minio/discussions/21655 https://github.com/minio/minio/discussions/21655 > I felt it might be appropriate for me to reach out as one of the stewards of the Docker Official Images program.
    • benterix 11mo ago
      Oh that will be an interesting discussion to watch.
    • Jeslijar 11mo ago
      So that's not the same thing. Docker "official images" are a category of curated docker images. Minio is not one of them. The official curated images are here: https://hub.docker.com/u/library https://hub.docker.com/u/library The minio image is basically a community one that anyone could have created, but still shows in overall docker hub. It's created by minio themselves. I'm kind of surprised they haven't removed it, but with over a billion downloads they are easily in the top ten of whatever category they fall under creating substantial free advertisement.
      • NewJazz 11mo ago
        Did you read the discussion? The docker steward is proposing making a docker "official" minio image to replace the minio/minio image.
        • Jeslijar 11mo ago
• ecshafer 11mo ago
  Ceph is an open source project run by a foundation. Minio is a company backed by VCs looking for a return. There is also seaweedfs, powerscale, openstack swift and hyperstore. The S3 compatible space is crowded.
  • Spivak 11mo ago
    Ceph is absolutely lovely and rock solid. Can't recommend it enough.
  • NewJazz 11mo ago
    Curious about one thing - does Ceph's s3 compatible api support oidc based auth? We used to use this with minio before switching to aws s3 and using presigned URLs. https://docs.min.io/enterprise/aistor-object-store/administration/iam/identity/oidc-identity/ https://docs.min.io/enterprise/aistor-object-store/administr...
  • __turbobrew__ 11mo ago
    As a user of Ceph it does feel like a truly open source project. Redhat/IBM do sponsor a lot of work on the project but there are lots of other contributors. I have contributed maybe a dozen changes myself and it was quite easy to do and the maintainers are fairly responsive.
  • okl 11mo ago
    Also there is garage, which I found easy to setup: https://garagehq.deuxfleurs.fr/ https://garagehq.deuxfleurs.fr/
• baq 11mo ago
  > We’ve started distributing our software for free > nice > We’ve stopped distributing our software for free > How dare you!
  • elAhmo 11mo ago
    That is not the problem here.
    • idkcomputers 11mo ago
      You're right. This is like they've stopped offering free gift wrapping. You can take it home in the plain package for free if you want.
      • pixl97 11mo ago
        It's been talked to death in other threads already, but typically when you provide a service, even if it's free, it is polite to give warning that you will stop providing said service in the future. If they are trying to push people to commercial services I typically attempt to steer away from companies that make rash decisions with a moments notice, rather than ones that would leave you high and dry.
        • nicce 11mo ago
          > It's been talked to death in other threads already, but typically when you provide a service, even if it's free, it is polite to give warning that you will stop providing said service in the future. They actually did that by saying that there are no new releases planned and new releases may be cut at anytime and everyone uses them at their own risk. https://github.com/minio/minio/commit/9e49d5e7a648f00e26f2246f4dc28e6b07f8c84a#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5 https://github.com/minio/minio/commit/9e49d5e7a648f00e26f224...
          • malicka 11mo ago
            … that commit is from last week. One week is not at all a sufficient warning, that’s rash and makes them look quite bad. Practically manic.
• antiloper 11mo ago
  `docker build` is free, and faster to type than the fake outrage in the github issues and the dicator-calling below in this thread.
  • jeroenhd 11mo ago
    With docker build comes a whole slew of dependencies that you wouldn't have with official images. You need some place to host the image, or build on the servers you use for deployment, and cross platform compilation (i.e. ARM images) becomes an issue. It'll take more time than just typing out a comment on HN to get all of that in play. Actually getting a docker registry of your own set up with auth and everything can easily take half an hour, and adding+testing periodic sync and compile steps in your CI/CD will take another couple of hours if you're not set up for it. Hardly the end of the world, though. Reminds me of the infamous "why can't people on github just give me the .exe" reddit troll post.
• deleted 11mo ago
  [deleted]
• lnxg33k1 11mo ago
  Since the whole docker thing where people were complaining about having to pay 10USD, I am happy when OSS projects pull the rug, tech bros you're paid to solve your company's issues, nobody in OSS owes you anything, go earn your salary and build the docker image that fix the CVE, or stfu We all know you don't care about loyalty correctness or anything, you just someone to do the work you're paid for
  • hansmayer 11mo ago
    Spot on. The number of people who are seemingly completely lost without a free DockerHub build is terrifying. Maybe it explains why software quality has degraded so much over the last several years.
    • cyanydeez 11mo ago
      are you saying there's a bunch of human centipedes bopping around here who are both the people who would do the minio rug pull as the ones who complain about not getting free services?
      • lnxg33k1 11mo ago
        pffff how boring
      • hansmayer 11mo ago
        It is hardly a rug pull, when they are still giving away the full source + the actual Dockerfile, so you know, you can build the image. In either case, if you are not running your own registry and are unable to build an image, but still complain about this minor issue...you are probably in the wrong business.
  • deleted 11mo ago
    [deleted]
• giorgioz 11mo ago
  I was not familiar with MinIO until this post and I see now 694+ upvotes! Can anyone give me some background on why MinIO is/was so used? So many people want to self-host S3 compatible software? Just asking, very curious about the whole thing!
• nicce 11mo ago
  It is unfortunate, but somewhere you need to draw the line, if you are planning to stop releases. If they fix this, how about the next? Why fix this one but not the next CVE? Is the reaction same next time and they end up fixing endlessly?
  • jeroenhd 11mo ago
    IMO they should've waited at least a month after updating their README. The timeline is rather short. It'll be hard to convince people to buy their commercial offering after pulling something like this. On the other hand, they did the work for free, so it's up to them to decide when to stop doing that. Plus, anyone can fork the repo and maintain their own version with fixes and docker images and everything.
• antiloper 11mo ago
  To everyone who gets blocked by this: I prompted Haiku 4.5, Anthropic's cheapest current model, in Claude Code with "Read this github issue: https://github.com/minio/minio/issues/21647 https://github.com/minio/minio/issues/21647 I need a new docker image for the latest minio version. Make it so.". It wrote a Dockerfile, I asked it to build it (not only am I incapable of finding and downloading the Dockerfile from the repository myself, I'm even incapable of remembering how to "build" a "docker"file). It spew out an error which the cheapest model promptly fixed and gave me an image. You need to be able to do this personally or you should not be running a durable storage cluster in-house. Just pay AWS. You need to add more value to your employer than you cost, and if Anthropic's cheapest model can beat you at such a task then it's not a good look.
  • switchbak 11mo ago
    > you should not be running a durable storage cluster in-house If you’re running Minio, odds are you have interesting use cases that are not filled by S3. I wouldn’t make such blanket statements. I don’t think anyone is surprised that an LLM can help you here either.
  • tristor 11mo ago
    I'm trying to be charitable here, but you're being incredibly obtuse in your response. The issue here is very much not that someone has to build a Docker image. There's already a Dockerfile in the repo that works to build it, you didn't even need some LLM to do that for you. That's not the issue. The issue is that their existing Docker image has billions of downloads and they simply stopped publishing updates unilaterally with no material attempt to communicate this to their users when the current image is affected by a critical CVE that will now never be fixed. If you don't understand the difference between these two issues, I would suggest it is /you/ that lacks the ability to add sufficient value to your employer (as if that's even a standard we should care about We are people, not merely cogs in some VC's wet dream).
    • jeroenhd 11mo ago
      The LLM stuff aside, how is minio supposed to communicate with the people who pulled their docker image? The time line is rather short (the README announcing source only releases got updated a week and half ago) but it's not like Docker will let you email everyone and say "you're using one of our products, read this post about our new distribution model", probably for good reason. I can only imagine the "vulnerability" warnings flooding the world if every pulled container opened an avenue for emails. I wouldn't buy their weird AI product off them after they behave like this, but this is software they've been maintaining and giving away for free, for years. Unless you have a contract with them where they promised maintenance, I don't see why this is on them, really. The company can go bankrupt tomorrow and you won't even be able to pay them to update their images. Maintaining your dependencies is your responsibility, especially if you're not paying them a dime.
• GZGavinZhao 11mo ago
  What makes me sad is that, as mentioned in other threads, this destruction in reputation could've totally been avoidable. If MinIO had took the time to give out warnings months in advance and help community members (or even other companies) to host the Docker builds somewhere else, there would've be close to none backlash. Yet they've decided to make it such an abrupt transition and especially when a CVE is involved.
• AtNightWeCode 11mo ago
  Still don't get why on earth anybody would run a Docker version of MinIO in production. And why is this even a problem. Not like you put a private storage service on the Internet? Or do you? The incompetence of the average HN user is just mind blowing.
• yencabulator 11mo ago
  In May, they pretty much said they will not maintain the "community version" anymore. Exact quote: "it will remain as is, and will only receive security fixes if any” https://jamesoclaire.com/2025/05/27/how-to-self-host-your-own-s3-in-2025/ https://jamesoclaire.com/2025/05/27/how-to-self-host-your-ow... They've also tried to claim AGPLv3 will infect any networked client code too: "Combining MinIO software as part of a larger software stack triggers your GNU AGPL v3 obligations. The method of combining does not matter. When MinIO is linked to a larger software stack in any form, including statically, dynamically, pipes, or containerized and invoked remotely, the AGPL v3 applies to your use. What triggers the AGPL v3 obligations is the exchanging data between the larger stack and MinIO." -- they've since removed that, utterly unsupported, argument, but the lesson to take home is they're really trying to prevent any non-paid use. It really is time to stop using Minio.
• __bjoernd 11mo ago
  Am I getting this right - someone has been providing things for free for a long time and now people are complaining that they are relying on getting things for free and the "someone" cannot just change this?
• Havoc 11mo ago
  At this stage I’d be hesistant to build anything on top of minio