12,964 karma · joined May 12, 2010
This tech has completely changed the sysadmin landscape/job descriptions and sort of threw tons of gas the whole devops movement.
Disclaimer: I worked at both Docker & Google. Although not on this tech specifically. Opinions are my own here.
A personal note here too. cgroups were invented at Google in the early 2000's. If you're using search today, gmail, docs, maps, etc. You're using cgroups. It sounds simple but this tech really powered a whole wave of innovation/startups/projects that almost everyone interacts with on a daily basis. Either through touching a Google service or interacting with anyone using Docker or Kubernetes (running on cgroups/namespaces). Pretty impressive.
#14 - Introduction to Linux Control Groups (Cgroups)
https://sysadmincasts.com/episodes/14-introduction-to-linux-...
#24 - Introduction to Containers on Linux using LXC
https://sysadmincasts.com/episodes/24-introduction-to-contai...
If you want a job at something like gitlab. Hangout on their open-source project, learn their codebase, and send in patches. Even if they are simple docs patches. Send in 50 of those and you will start to learn the devs. Ask one of them what it is like to work there, ask them to refer you, etc. The CEO of gitlab is constantly on HN (I swear he has an alert for mention of gitlab). So, he will likely see this post. My point, take some initiative and try not to go through the conventional recruiter pipe (apply on website and no one ever gets back to you cycle). Doing this, has worked out really well for me in the past, and it will work for you too. Sure, it is more work but gets you ahead of everyone else as you are making an effort. Be strategic about this and really choose who you want to work for and go after them. Having something like, hey, I patched 50 minor typos in your code/docs goes a long way, between you and some nobody!
Nick, long time no see. Hope thing are well. Amazing who you find browsing these threads :)
I imagine eventually, you could have some type of transcript that's annotated with speech synthesis markup language (SSML). Then, you have a CI/CD pipeline that would run this text-to-speech engine and regenerate the audio. I could then pair this up with the video. I honestly wonder if we are a year or two away from this being possible.
This thread has a good answer: https://news.ycombinator.com/item?id=16976392
> "containers do not contain"
Is sort of troll bait. They do contain. That is why everyone is using them. Sure, there will be exploits to break out of them, just like with VMs, and even CPU bugs now.
Here is a good example of someone who broke out of a container on the play-with-docker.com site using a custom kernel module [1]. This allowed a container escape but you could say this was a bug since that wasn't the intent. So, you'd patch it. So, I get the joke in that people are extremely creative and will find ways around everything.
[1] https://www.cyberark.com/threat-research-blog/how-i-hacked-p...
[1] https://sysadmincasts.com/episodes/69-cloud-run-with-knative
> gVisor intercepts application system calls and acts as the guest kernel, without the need for translation through virtualized hardware. gVisor may be thought of as either a merged guest kernel and VMM, or as seccomp on steroids. This architecture allows it to provide a flexible resource footprint (i.e. one based on threads and memory mappings, not fixed guest physical resources) while also lowering the fixed costs of virtualization. However, this comes at the price of reduced application compatibility and higher per-system call overhead.
From what I understand, basically a user-space program that wraps your container and intercepts all system calls. You can then allow/deny/re-wire them (based on a config). So, you have pretty much complete control over what your apps can do.
This for me, is sort of the key takeway from the blog post too: "because we use gVisor to increase the security of Google's own internal workloads, it continuously benefits from our expertise and experience running containers at scale in a security-first environment". So, Google's using something like this internally too for their own workloads, which should be a pretty good sign this works in real life.
[1] https://gvisor.dev/docs/architecture_guide/
> Some employees said they waited at their desks the rest of the day for news about who would be affected. The majority of the cuts were in North America and Asia, with the Singapore office being closed entirely, according to a post from one employee. The company’s European workforce also saw reductions."
> “The way this was handled…was insane,” wrote one employee. “You try sitting all day with that email hanging over your head and then being let go and bundled out the door as if you are a risk to company moral [sic] – as if anything could be more demoralizing than seeing valued colleagues get frog marched out of the office as they are crying. Absolute shit show.”
I wonder if there is a management chapter somewhere that walks you through how to do a mass layoff? Telling everyone to sit at their desks and wait to see what happens.. seems like a bad option. I guess there are no real good options here but this seems extremely stressful and rushed.
Same thing happened with cell phones. You used to have a walkman, dvd/cd player, a camera, a calculator, a pager, flashlight, notepad, etc. Now, you just have a phone.. add the gaming console to this list (and most other electronics too).
> A malicious server could send a specially crafted packet which could result in an unchecked integer overflow. The value would then be used to allocate memory causing a possible memory write out of bounds error (CWE-130). [1]
Maybe now we can put a stop to all these ssh bots crawling the internet. Just setup a malicious ssh server ;). This CVE was part of a larger release of nine separate security advisories concerning libssh2 [2].
[1] https://www.libssh2.org/CVE-2019-3855.html
[2] https://www.openwall.com/lists/oss-security/2019/03/18/3
Except you'll be competing with patio11 so watch out.. haha. Nice seeing your comment here and want to echo about the writing what you learn part. This will help refine your ideas too. It also puts you on the map and you will start to build up a portfolio of sorts. This is great advice.
[1] https://ai.google/research/pubs/pub36356.pdf
[2] https://ai.google/research/pubs/pub39966.pdf
This appears to be the accompanying blog post. So, not a dupe and explains the higher level goal here. The post from yesterday, was before the product was actually publicly released, if that gives more context as to why this is new news.