cpuguy83

28 ms·

361.
by cpuguy83 4y ago
Key word here is "almost". No need to get bent out of shape, especially when the Tesla didn't. /s
362.
by cpuguy83 4y ago
Excuse is no need to do port forwards.
363.
by cpuguy83 4y ago
If all you are looking for is noise reduction, use a dynamic mic instead of a condenser. Example condenser mic: Blue Yeti You'll see a lot of streamers use these kinds of mics because you don't need to be right up on it. Example d
364.
by cpuguy83 4y ago
Or just dampening the ambient sound?
365.
by cpuguy83 4y ago
Mainly record high inflation and the gas crisis (which was way worse than today's). Whether or not anyone could have stopped that doesn't matter, ppl attribute this to him.
366.
by cpuguy83 4y ago
"The user" being the entity that sets up the vm. It requires the share to be added to the vm and then a command to be run to register it with the Linux kernel.
367.
by cpuguy83 4y ago
Most likely Docker Desktop would have an option to toggle between Rosetta and qemu. Docker Desktop manages the vm, so it would be up to it to mount the Rosetta share into the vm and register it with binfmt.
368.
by cpuguy83 4y ago
Yes qemu and Rosetta perform the same basic role here (bintfmt handler for x86 bins), but Rosetta should perform significantly better (otherwise there would be virtually no reason at all to build this).
369.
by cpuguy83 4y ago
The way this would work is Docker would be setting this up for you (maybe through some option to switch between qemu and Rosetta). The containers should not need the mount. What happens is Rosetta gets registered with the kernel (binfmt_mis
370.
by cpuguy83 4y ago
The whole point in providing Rosetta is because it (should) be significantly faster than plain qemu.
371.
by cpuguy83 4y ago
Docker Desktop (ie Docker on Mac) absolutely sets up a VM.
372.
by cpuguy83 4y ago
Instead of running in qemu (as it currently would), it would run under Rosetta.
373.
by cpuguy83 4y ago
I don't know about "production container workflows" on a Mac, however the only thing that needs to be done is to use the new Rosetta binfmt handlers instead of qemu (which Docker Desktop already sets up for you). I imagine Do
374.
by cpuguy83 4y ago
It's really going to depend on how well arm64 is supported in your stack. If arm64 versions are just available then you really shouldn't see a difference. That can be a big if, though. And otherwise you are stuck running everythin
375.
by cpuguy83 4y ago
This is very much a normal thing pre-pandemic. Get used to it, kids are gross, do gross things, don't wash, snot everywhere, etc. - Parent of 3
376.
by cpuguy83 4y ago
Web rings!
377.
by cpuguy83 4y ago
$25 billion... thinking about how much money we've dedicated for active warfare in the last 2 months alone... clearly we have our priorities.
378.
by cpuguy83 4y ago
The notion that RH kernels are stable is patently false. RH constantly backports features to "stable" kernels, and it does cause problems. I was on the forefront of this when they were backporting container tech to their 2.6.32 ke
379.
by cpuguy83 4y ago
32-bit pi is not a niche device. - Load up Debian - install cross-build-essential - dpkg --add-architecture armhf - install the lib you want to link - set "CC" to the armhf compiler - go build
380.
by cpuguy83 4y ago
Compile in Debian. It has a full cross compile tool chain and is as simple as adding the target architecture to dpkg to get the libraries you need (assuming you don't mind the versions packaged for Debian). Getting the right libs is re
381.
by cpuguy83 4y ago
We also don't have space robots...
382.
by cpuguy83 4y ago
Mining for resources, either to send back or for future human landings.
383.
by cpuguy83 4y ago
Haven't we lost satellites that are just orbiting our own planet?
384.
by cpuguy83 4y ago
An phenomenal read on how it works: https://tailscale.com/blog/how-nat-traversal-works/
385.
by cpuguy83 4y ago
Tailscale's data plane is [1] mostly p2p except for some cases where it doesn't work and it goes through an encrypted relay. So your data does not run through Tailscale servers. There is an oss [2]coordination server that does let
386.
by cpuguy83 4y ago
Volumes are mapped in already. They get mounted to the containers rootfs dir, and that is used as a preopen for wasi. https://github.com/deislabs/runwasi/blob/9a43a31c1f29df65392...
387.
by cpuguy83 4y ago
The main advantage to doing it at the shim level is I can run multiple wasm containers from a single wasm runtime more easily. I did look at implementing this at the OCI layer (also really cool that crun does this!) but decided to go anothe
388.
by cpuguy83 4y ago
It gets setup fairly similarly to how you would run a "normal" runc container. containerd passes along a path to the rootfs of the container (for wasi I'd expect to be just the wasm module) which is built from the OCI image a
389.
Show HN: Run WASM in Containerd(github.com)
77 points by cpuguy83 4y ago|11 comments
390.
by cpuguy83 4y ago
Are you mapping your source code from the host to the vm?

More ›