errordeveloper

4 ms·

1.
by errordeveloper 6y ago
Userspace networking had been around for quite a few years, yet didn't seem to have taken off, despite all the great benchmarks... I think the main blocker is that you cannot make apps use it without hacks. It looks like Snap requires
2.
by errordeveloper 9y ago
Not everyone had the same experience. There a few minor UX flaws that make it frustrating to use, e.g. having to set Docker host, shared filesystem performance is poor, networking in enterprise desktop environment is broken (just to name a
3.
by errordeveloper 9y ago
It will be possible to run all your add-ons in the local setup, including networking. Multi-node is essential for some use-case, but arguably is not critical for most people, yet it is coming in the future.
4.
by errordeveloper 10y ago
At Weaveworks, we have a built a tool called Flux [1]. It is able to relate manifests in a git repo to images in container registry. It has a CLI client (for use in CI scripts or from developer's workstation), it also has an API server
5.
by errordeveloper 10y ago
Yeah, the point is that you should need to buy any hardware even for development, which is the biggest win to me!
6.
GoshawkDB: A distributed, transactional, fault-tolerant object store(goshawkdb.io)
87 points by errordeveloper 11y ago|45 comments
7.
Kaws – A tool for deploying multiple Kubernetes in AWS with CoreOS+Terraform(github.com)
2 points by errordeveloper 11y ago|0 comments
8.
by errordeveloper 11y ago
Right, if you know how to set it up or have infrastructure in place... But most developers don't have time to read 600+ pages on how to run bind server OR simply have ops team that is very conservative at what goes in the DNS land.
9.
by errordeveloper 11y ago
Well, adding a library for supporting SRV records is not simple... If you use Weave [1], it gives a unique IP address to every service instance and a DNS record, all with zero configuration. That means you just stick any service in whatever
10.
by errordeveloper 11y ago
It's really great to hear this is all happening now!
11.
by errordeveloper 11y ago
Hello, author is here, do let me know if you have any questions!
12.
Multi-Host Docker Deployment with Swarm and Compose Using Weave 0.11(blog.weave.works)
6 points by errordeveloper 11y ago|1 comments
13.
by errordeveloper 11y ago
For example, here is the guide on using Weave for Kubernetes on Azure cloud: https://github.com/GoogleCloudPlatform/kubernetes/blob/maste...
14.
by errordeveloper 11y ago
I like OSv, just because it doesn't have TTYs.
15.
by errordeveloper 11y ago
OSv is a unikernel and isn't a container... but anyway, good point!
16.
by errordeveloper 11y ago
Yes. Grepping the code or fighting runtime errors are two complementary approaches I can think of... Not sure if there are other methods.
17.
by errordeveloper 11y ago
They don't have to, one can run static binary without any problems. It's just that most people keep throwing in a whole distro...
18.
by errordeveloper 11y ago
The exact approach described here is very extreme. It's a top-down method with a tool. I find the tool may be of some interest, but I think bottom-up method would be more practical . I have done some experiments with Yocto/OpenEmb
19.
by errordeveloper 11y ago
Well done, Kai! Cannot wait to try it out ;)
20.
by errordeveloper 11y ago
That'd be pretty amazing!
21.
by errordeveloper 11y ago
I have recently found this: https://github.com/rustcc/coroutine-rs
22.
by errordeveloper 11y ago
There is a lot community effort being put into Docker extensions to enable production use cases like what you have just mentioned.
23.
by errordeveloper 11y ago
In theory one can reimplement Node on Go runtime, instead of libuv and other libraries Node uses for binding the V8 to the OS.
24.
Kubernetes on Azure with CoreOS and Weave(github.com)
2 points by errordeveloper 12y ago|0 comments
25.
by errordeveloper 12y ago
Luke, congrats for releasing it!
26.
by errordeveloper 12y ago
Kai, it's really awesome to see this finally out!
27.
by errordeveloper 12y ago
Do checkout the demo [1] I and Luke did earlier, using Powerstrip adapters for Weave and Flocker. It shows how a database container can be moved from one machine to another, keeping it's data and IP address! [1]: https://www
28.
by errordeveloper 12y ago
I don't think it would be hard to use Kubernetes with Powestrip and Flocker. I and Luke worked on integrating Weave with Flocker together last week, and Powerstrip makes it really quite simple. There is not much that would get on the w
29.
by errordeveloper 12y ago
What would you do? You will write code in Go to create flexible, easy-to-use tools for containers in development and in production. You will design and implement new tools for monitoring and managing container networks. You will help shape
30.
by errordeveloper 12y ago
Core Engineer at VC-funded open-source project, Weaveworks, London Weaveworks is a start-up founded by the team that created RabbitMQ and backed by one of the world’s leading tech investors. Headquartered in London, we are hiring engineers

More ›