Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
amouat
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
61.
▲
Linux Capabilities in Practice
(blog.container-solutions.com)
3 points
by
amouat
7y ago
|
0 comments
62.
▲
Installing a Registry on Kubernetes Quickstart
(container-solutions.com)
1 points
by
amouat
8y ago
|
0 comments
63.
▲
Programming Languages for Microservices (and Containers)
(container-solutions.com)
3 points
by
amouat
8y ago
|
0 comments
64.
▲
by
amouat
8y ago
I'm a little confused by this. I get the specification is cloud agnostic. But it looks like the developer needs to write the underlying code to provision and maintain the application on the various clouds. It feels like a too thin abst
65.
▲
by
amouat
8y ago
I think we should avoid commenting about the dev's background. It was clearly a company decision and the discussion should be at that level.
66.
▲
by
amouat
8y ago
Yeah, it should do that. You can read up on how the kubelet and Linux OOM work in k8s here https://kubernetes.io/docs/tasks/administer-cluster/out-of-r... . Once the OOM kicks in though, I think you're in
67.
▲
Image Management and Mutability in Kubernetes
(container-solutions.com)
2 points
by
amouat
8y ago
|
0 comments
68.
▲
by
amouat
8y ago
This almost exactly mirrors my experience. I really hate when questions get closed. Fixing it would take such a change in direction and leadership that it looks unlikely to happen. It seems such a shame.
69.
▲
by
amouat
8y ago
Kaniko does run in the container as root, but the container doesn't need to be granted any extra privileges when run (you don't need the equivalent of Docker's --privileged flag).
70.
▲
by
amouat
9y ago
As a small counterpoint, I did notice some people did very well at Advent of Code using Rust e.g. sciyoshi was 4th overall. https://adventofcode.com/2017/leaderboard https://github.com/sciyoshi/adv
71.
▲
A Trip from the Past to the Future of Kubernetes
(blog.giantswarm.io)
2 points
by
amouat
9y ago
|
0 comments
72.
▲
by
amouat
9y ago
Agreed. I think they mean it's rare in terms of subject matter and style. If you want a painting of a fruit bowl, that's easy to find, but this, not so much...
73.
▲
by
amouat
9y ago
Docker for Mac and Windows will include a single node k8s cluster, so yes, effectively a replacement for minikube. Docker EE will include full support for k8s as an orchestrator as well as Swarm mode.
74.
▲
by
amouat
9y ago
Yes. And I don't mean to knock minikube, but this is potentially simpler and easier to use.
75.
▲
by
amouat
9y ago
This really helps with the dev-to-production story for containers. When people first started using Docker containers, we were promised things would run identically in dev and production - no more "but it worked on my laptop" issue
76.
▲
by
amouat
9y ago
Sure. And having read (part of) the paper, the point was more about reuse than abstraction (though they are obviously related concepts).
77.
▲
by
amouat
9y ago
Or perhaps McIllroy fully understood that and wanted to make the point that programming with higher-level abstractions makes software easier to document and understand. It's hard to say without being able to read the original article.
78.
▲
by
amouat
9y ago
Also note github repo at https://github.com/nginx/unit
79.
▲
by
amouat
9y ago
The thing is, it's not as easy as it sounds - take a look at the issues on the official image :(
80.
▲
by
amouat
9y ago
They have their own installer now, that must have taken a _lot_ of work. I think they'd have been much better served by producing a Docker image and telling self-hosters to use that. Would have been easier, much more portable and less
81.
▲
by
amouat
9y ago
A look at the recent commits would suggest they are correct: https://github.com/ethereum/solidity/commit/e506129aee5745e2...
82.
▲
by
amouat
9y ago
> Pretty code is easy when it's a few people writing it. Harder when it's a team of tens / hundreds Yeah, this is a good point that I was overlooking. It's easy for me to be critical when I feel the pain digging throu
83.
▲
by
amouat
9y ago
I know very little Go, but I have seen the Kubernetes code and my impression was "I bet these people were Java programmers in a past-life". You could tell by the multiple layers of abstraction, a lot of which felt unnecessary. Hav
84.
▲
by
amouat
9y ago
I agree it can take a long time to prepare a keynote worthy talk. However, it certainly can be lucrative, take a look at http://www.dailymail.co.uk/news/article-1167682/Blair-worlds... (apologies for linking a Dai
85.
▲
by
amouat
9y ago
It's unusual to be paid to give a talk, unless it's a keynote or the organisers know that your name (or your organisation's name) will sell more tickets. Keynote speakers with a big reputation can get paid a lot of money fo
86.
▲
by
amouat
9y ago
Same...
87.
▲
by
amouat
9y ago
Personally, I think this a great move for the community, but the reasoning and implications could have been made a little clearer. The intention is to have a clearer split between the Open Source community project - which is and will always
88.
▲
by
amouat
10y ago
Well they got a banking licence recently https://monzo.com/blog/2017/04/05/banking-licence/ I don't really understand why you pick on 32-bit/64-bit. I assume you wouldn't touch floati
89.
▲
The 2017 Docker Usage Report
(sysdig.com)
3 points
by
amouat
10y ago
|
0 comments
90.
▲
by
amouat
10y ago
Note that the pricing is per node.
More ›