I hit this at work a few weeks ago. At least then, the aws public ecr still had all the images cached and tagged. It was relatively straightforward for us to pull the ones we were using then tag...
I hit this at work a few weeks ago. At least then, the aws public ecr still had all the images cached and tagged. It was relatively straightforward for us to pull the ones we were using then tag and push them to our own ECR registry, then update our image references. But, we were already using AWS and ECR so YMMV.
Obviously that is only a short term fix, but it takes it from "oh shit" to "we'll get around to it" and also gives you some time to wait and see how the community responds.
It's really not that hard to pull the latest tag, apply your own fixes, and then document and version it internally. You are running a private container registry, right? The thing that is most...
Use “latest” tags: Abandon version control, risking deployment chaos, compatibility issues and compliance violations.
It's really not that hard to pull the latest tag, apply your own fixes, and then document and version it internally. You are running a private container registry, right?
The thing that is most amusing to me is that this entire crisis is not that big deal to people who still have sysadmins on staff. A decent number of them likely still have bash scripts and makefiles to bring any system to production-ready inside a day.
I left a company of 105,000 to join a startup of < 40 people. There is no sysadmin here nor will there be for a long time. But there are a small core of people with the right mindset that are...
I left a company of 105,000 to join a startup of < 40 people.
There is no sysadmin here nor will there be for a long time. But there are a small core of people with the right mindset that are welcoming and open to new ideas.
We dealt with the bitnami rug pull quickly and easily. In the meantime, hearing from my prior team dealing with it? Bit of a nightmare, but they're fine too.
It's not a gigantic thing. But it is a constant reminder to have every dependency internal and keep that mistrust muscle exercised.
Plenty of 'devops'/infra people have healthy homelabs and know what to do ... The sysadmin line just feels a little superior and gatekeepy.
To be fair, I mostly consider devops to be a rebranding. Same shit, different tools and expectations. My main crankiness is the love of YAML in the new tooling. I love the tools that use it, but...
To be fair, I mostly consider devops to be a rebranding. Same shit, different tools and expectations.
My main crankiness is the love of YAML in the new tooling. I love the tools that use it, but dear lord it gets out of control easily.
In the middle of the article it lapses into "increasingly breathless Markdown headings and lists" style. We have "Dependency Hell Multiplied" and "Legacy Repository Limbo" and a bunch of sections...
In the middle of the article it lapses into "increasingly breathless Markdown headings and lists" style. We have "Dependency Hell Multiplied" and "Legacy Repository Limbo" and a bunch of sections with three bullet points, where each bullet has its own boldface key point, and the negativity and fear is relentless.
Does everybody on Medium write like this, when they write these blog posts that are really about how their product solves $problem_of_week? Is that where the robots get it? Or was this section on "what are the potential problems this could cause my readers" maybe synthesized to spec to make writing the post faster? Or are actual people starting to write like this now, having seen too much of it?
It's not that I begrudge a corporate blogger a text generator, but I've seen this shape of text too much while being bullshitted by an instruct-tuned model that I have asked for something which it is really incapable of delivering. It is is maybe trying to make up for in formatting and stridency what it is failing to dredge out of its few billion weights in actual useful information, and hide the fact that it is just restating the obvious from whoever is being paid a piece rate to rank the responses. So when I see it in the wild it sets off my BS detector, and I feel inspired to try and reboot whoever is talking to me.
Yeah thats just Medium. I tried to find another article that had all this info in a format that wasnt a github pr but… this was it. I do think this is where the LLMs got it from
Yeah thats just Medium.
I tried to find another article that had all this info in a format that wasnt a github pr but… this was it.
Haven’t seen this on here in the past day but I use Bitnami images and its been a hell of a time swapping to other images.
I hit this at work a few weeks ago. At least then, the aws public ecr still had all the images cached and tagged. It was relatively straightforward for us to pull the ones we were using then tag and push them to our own ECR registry, then update our image references. But, we were already using AWS and ECR so YMMV.
Obviously that is only a short term fix, but it takes it from "oh shit" to "we'll get around to it" and also gives you some time to wait and see how the community responds.
This is what we did too. Theres someone somewhere making a long term plan but not me, onto the next crisis for me…. Haha
It's really not that hard to pull the latest tag, apply your own fixes, and then document and version it internally. You are running a private container registry, right?
The thing that is most amusing to me is that this entire crisis is not that big deal to people who still have sysadmins on staff. A decent number of them likely still have bash scripts and makefiles to bring any system to production-ready inside a day.
I left a company of 105,000 to join a startup of < 40 people.
There is no sysadmin here nor will there be for a long time. But there are a small core of people with the right mindset that are welcoming and open to new ideas.
We dealt with the bitnami rug pull quickly and easily. In the meantime, hearing from my prior team dealing with it? Bit of a nightmare, but they're fine too.
It's not a gigantic thing. But it is a constant reminder to have every dependency internal and keep that mistrust muscle exercised.
Plenty of 'devops'/infra people have healthy homelabs and know what to do ... The sysadmin line just feels a little superior and gatekeepy.
To be fair, I mostly consider devops to be a rebranding. Same shit, different tools and expectations.
My main crankiness is the love of YAML in the new tooling. I love the tools that use it, but dear lord it gets out of control easily.
Yeah it took us about two days.
Was a hell of a two days though.
In the middle of the article it lapses into "increasingly breathless Markdown headings and lists" style. We have "Dependency Hell Multiplied" and "Legacy Repository Limbo" and a bunch of sections with three bullet points, where each bullet has its own boldface key point, and the negativity and fear is relentless.
Does everybody on Medium write like this, when they write these blog posts that are really about how their product solves $problem_of_week? Is that where the robots get it? Or was this section on "what are the potential problems this could cause my readers" maybe synthesized to spec to make writing the post faster? Or are actual people starting to write like this now, having seen too much of it?
It's not that I begrudge a corporate blogger a text generator, but I've seen this shape of text too much while being bullshitted by an instruct-tuned model that I have asked for something which it is really incapable of delivering. It is is maybe trying to make up for in formatting and stridency what it is failing to dredge out of its few billion weights in actual useful information, and hide the fact that it is just restating the obvious from whoever is being paid a piece rate to rank the responses. So when I see it in the wild it sets off my BS detector, and I feel inspired to try and reboot whoever is talking to me.
Yeah thats just Medium.
I tried to find another article that had all this info in a format that wasnt a github pr but… this was it.
I do think this is where the LLMs got it from