Live data from Hacker News

Viewing profile — mikesir87

mikesir87

HN member
Joined
Mon, Oct 24, 2022, 7:59 PM UTC
HN karma
95
Public activity
19 items

About mikesir87

DevRel at Docker

Recent public activity

  1. comment
    Comment #49248092

    For clarity, there is no "search and replace" function going on. It's only setting the header. The main reason a "proxy-managed" env var is set is because most CLI tools assume if …

  2. comment
    Comment #49246638

    The secrets are stored in the OS-specific keychain. When a sandbox starts, the network proxy injects the secret into the request (as auth headers) only when the hostname matches. R…

  3. comment
    Comment #49245028

    Disclaimer - on the Docker DevRel team One of the demos I run is how easy it is to circumvent the harness limits. For example, I can configure a harness not to access file `secrets…

  4. comment
    Comment #49244961

    When starting a sandbox, you can specify the mountpoints you want. It just defaults to the current directory. You can also specify some of those mounts as read-only as well. Exampl…

  5. comment
    Comment #49244898

    Thanks for the feedback! Will pass it on to the web team to get this more mobile-friendly.

  6. comment
    Comment #49244875

    On the Docker DevRel team... yes! This is it. The secret is injected only into headers in which the hostname matches. There's also an ability to create kits where you can setup cre…

  7. comment
    Comment #44444908

    Excited to see models get first-class support! Will be interesting to see what opportunities this opens with this being formalized (other tooling/integrations, etc.). Note that Com…

  8. comment
    Comment #35188691

    (from the Docker DevRel team) "During that period" refers to the 30-day period. During that time, the images are accessible. After the 30-day period, they will still be pull-able, …

  9. comment
    Comment #35188603

    (from the Docker DevRel team) Ha! Just had to say... this gave me a good laugh! We're trying to get better... I swear! Comms are hard. We'll get there.

  10. comment
    Comment #35188311

    (from Docker DevRel team) > Given these statements directly contradict each other Actually... they aren't contradictory. The organization data will be retained for 30 days and is s…

  11. comment
    Comment #35187628

    (Docker DevRel team here) For clarification, the program grants one year of access, but is indefinitely renewable as long as the program is still compliant with current criteria.

  12. comment
    Comment #33330830

    Great question! In the demo app we showed yesterday (source here - https://github.com/second-state/microservice-rust-mysql ), the Dockerfile is leveraging a multi-stage build where…

  13. comment
    Comment #33330751

    > So docker+WASM does not build a Linux container image with the WASM application inside but it builds a WASM application packaged as a docker image With this preview, we are lever…

  14. comment
    Comment #33326173

    Sorry for the delayed response, but the problem we're trying to help solve is how to help lower the barrier of entry to using Wasm apps leveraging the tool many developers are alre…

  15. comment
    Comment #33322880

    Great question! The promise (and excitement) of Wasm is to have portable, secure, quick-to-start, and low resource usage apps. So, write code in Go, Rust, C++, or any other languag…

  16. comment
    Comment #33322746

    There are a few things we're excited about, many of which we fully recognize are used in marketing/buzzword bingo. But, they really are around portability (compile to a Wasm module…

  17. comment
    Comment #33322630

    Great question! There isn't a way to run Docker directly in the browser. But, there are tools (like Play with Docker at play-with-docker.com) that lets you interact with a CLI in t…

  18. comment
    Comment #33322600

    Depends on which "this" you're referring to. We (Docker) are trying to make it easier for developers to use the tools and capabilities they know and love to build, share, and run W…

  19. comment
    Comment #33322334

    Michael Irwin from Docker here (and author of the blog post too). Happy to answer your questions, hear feedback, and more!