mikesir87

7 ms·

1.
by mikesir87 1mo ago
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 the env var is set, auth is set. If
2.
by mikesir87 1mo ago
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. Read more about the secrets handling here - https:/&#x2
3.
by mikesir87 1mo ago
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.txt`. But, then I can immediately have it create a Python f
4.
by mikesir87 1mo ago
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. Example: sbx run claude ./ ../another-project:ro
5.
by mikesir87 1mo ago
Thanks for the feedback! Will pass it on to the web team to get this more mobile-friendly.
6.
by mikesir87 1mo ago
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 credential injection into other services as well.
7.
by mikesir87 1y ago
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 Compose files using the previous model declarations (using
8.
by mikesir87 4y ago
(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, but not able to be updated.
9.
by mikesir87 4y ago
(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.
by mikesir87 4y ago
(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 subject to deletion. That data includes the teams, me
11.
by mikesir87 4y ago
(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.
by mikesir87 4y ago
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 the first stage builds the Wasm module
13.
by mikesir87 4y ago
> 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 leveraging the OCI specification that defines how to build an
14.
by mikesir87 4y ago
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 already using. As an example example, with Docker+Wasm you
15.
by mikesir87 4y ago
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 language that can output to Wasm (up to over 40 now!) and you'
16.
by mikesir87 4y ago
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 and run on any architecture), isolated sandboxing
17.
by mikesir87 4y ago
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 the browser to run commands against a remote cloud insta
18.
by mikesir87 4y ago
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 Wasm applications. As far as Wasm itself, it&#
19.
by mikesir87 4y ago
Michael Irwin from Docker here (and author of the blog post too). Happy to answer your questions, hear feedback, and more!