HN user
co-founder of Umbraco, stints at Zalando, Spotify etc etc
Sandboxes are free, distributed outside of Docker Desktop, no license fee required - money is made on enterprise governance and cloud offerings.
You can call containers a commodity, or an industry standard? Feels like that is more an emotional argument than anything else.
2 different platforms, 2 separate sources of truths for policies, 2 different level of compatibility (apple containers don't support compose, MS uses a custom moby implementation, neither are particular mature), none has linux compatibilty?
Always assumed the SoMe sharing buttons was primarily motivated by the social sites to get their pixel on as many sites as possible to track behavior across sites
Company sells product for profit - they are liable for the product and all its subcomponents - there is nothing unfair about this - it doesn't matter if you found the components in a hole in the ground or on github - if you are selling a product based off it, you are liable.
For freelancers / oss companies - you can still sell services such as consulting or support - without selling your oss project - then its a service - not a product.
Uh, this looks very nice - reminds me of a TUI version of Canopy, if you are interested, We've (docker) been working on a separate agent sandbox runtime called SBX built around a MicroVM with a private docker daemon inside, maybe there's potential for a collaboration to add support for this runtime - feel free to ping me: per(dot)krogslund(at)docker .com
This article is from February - we have since shipped the microvm sandbox engine as a seperate binary: sbx - no docker desktop required, small 50mb binary.
https://docs.docker.com/ai/sandboxes/
Not sure how well their work maps to sbx, but there has been multiple releases with features and improvements since then
MicroVM based sandboxes for agents, with container support, in a small independent binary installable from brew/winget
Docker sandboxes uses a MicroVM as an additional isolation layer - its not just containers (as also mentioned in the nanoclaw post)
Outlining this as precision versus using 100s of thousands on chainguard, seems like 2 extremes pitted against eachother, when hardened images is largely free now: https://hub.docker.com/hardened-images/catalog
- Each agent runs in a dedicated microVM - agents can build and run Docker containers inside the MicroVM - no access to the host Docker daemon - network isolation with allow and deny lists - available for macOs and windows (linux support coming)
purely curious, but why did you go with ollama instead of the built in LLM runner in docker, since you are also using docker?
Remember interviewing for a security role at Phillip Morris who owns the IQOS e-cigaret brand. They bragged about how the device phoned home every time it could get a bluetooth or wifi connection, to inform of consumption amount and patterns - so they could proactively send users more nicotine.
He dramatically revealed that they were no longer selling tobacco, but rather "Nicotine as a service"
Needless to say, I decided not to work for a merchant of death
"We find that women’s relative earnings and employment increase by 4.4% and 2.9% respectively following the birth of the manager’s first daughter. These effects are driven by an increase in managers’ propensity to replace male workers by hiring women with comparable education, hours worked, and earnings."
For oss projects with heavy pulls, the (free) dsos programme removes all rate limits on their public images, the intention was never to impact projects, but rather mega corporations using hub as free hosting:
Projects are not charged for hub usage
Thanks for reporting, team is fixing it, the right url is: https://github.com/docker-hardened-images/catalog/issues/
0 results for "ketamin" I think this is broken
Exactly for this problem, the docker sandbox command was added to the cli - currently only experimental though:
the prevailing trends in locker-room design is privacy, a way to make “a diverse user base” feel comfortable.
One thing that annoys me about this article is the subtle stab at woke / gender identity as a reason for this change. Both Germany and Sweden has a much higher percentage of transgender people compared to the US, and neither have these kinds of locker rooms.
Living in Germany where all-gender nude changing rooms, nude all-gender saunas and nude beaches are very normal and very much not sexualised, it is striking how different the underlying culture is here - Germans find nudity practical and sanitary, and at the same time they very much insist that you wear special bathing shoes.
Docker Debug was previously a paid-for feature, now available for free since v4.49
I agree on principle, while at the same time I'm fairly sure the common employees at these respective companies are probably thankful that their job security is not impacted by their employer taking a (very small) stand.
From article: ads are also running on: HBO Max, X, YouTube, Amazon Prime Video, LinkedIn and Meta, as well as cable television channels.
And what choice do these platforms really have? They either run ice ads, or risk getting on the bad side on the administration.
Rate limits are primarily applied to unauthenticated users, open source projects and business accounts have none/much higher tresholds
Only norway has significant oil revenue - sweden and denmark specifically are primarily economies driven by a highly educated workforce and well regulated job markets - Lego, Novo, Maersk are all exemples of this kinds of companies depending on those socalled big government programmes to produce highly educated and specialised workers.
Of the scandinavian countries, only Norway has money, Dragsted is danish.
Havnt docker been cncf member for ages?
Anyone know the backstory of why Georg Wendt is on the memorial? He died in 1948 and atleast the wikipedia page doesn't outline whether he was murdered or related to the nazis?
Yeah, its the same underlying functionality that Depot, Docker Cloud Build and also Offload uses under the hood to switch the context to a remote host: https://www.docker.com/products/docker-offload/
While I generally agree with the author on code over tools, the article could have benefitted from some concrete ways that this could have potentially been done somewhat securely by sandboxing, enforcing zero trust, network segmentation, and all the other known controls we've developed over the last decade.
I love the optimism of this space, but fear that the "security is a sham" attitude will bite us all in the ass down the line.