HNHacker News
TopNewBestAskShowJobs

kylegalbraith

574 karma · joined September 6, 2017

Founder of https://depot.dev/

Blog at https://blog.kylegalbraith.com

Previously at: Era Software, Thorn, Zapproved

Previously built: https://ultimatefantasysupercross.com/ https://kylegalbraith.com/learn-aws/ https://kylegalbraith.com/learn-by-doing/

kyle@depot.dev

submissionscomments
kylegalbraith··on Show HN: Paclear – A Fun Twist on the 'Clear' Command with Pac-Man Animation
I wish it would adjust to the height of my terminal and do it all in one go instead of jumping down line breaks.
kylegalbraith··on Workloads on Arm-based AWS instances
We leverage Arm instances in Depot [0] to power native Docker image builds for Arm and I would say we see a lot of performance improvement in with machine start, requests per instance, and overall response rate. Granted, we aren't throwing the number of requests at our instances that this test is looking at. But, we are throwing multiple concurrent Docker image builds onto instances and generally speaking, they do great.

All of that to say, I think the t3/t4 instance used in this test is a bit problematic for getting a true idea of performance.

[0] - https://depot.dev/

kylegalbraith··on Workloads on Arm-based AWS instances
This is the first thought I had as well. The t3/t4 class is notoriously problematic when you get to reasonable loads because of their burstable nature. Still an interesting test, but it would be better on a general instance class.
kylegalbraith··on Burning money on paid ads for a dev tool – what we've learned
PostHog is a fantastic product and I really feel like they are becoming the company that is looking to broadly share their learnings/experience with others.
kylegalbraith··on Burning money on paid ads for a dev tool – what we've learned
We do a little bit of this with depot.dev and it doesn’t have meaningful conversion.

But, I do think it helps awareness as we do get some folks that tell us I saw you on this repo or that.

We also do it to support projects we think are neat/useful to others even if we don’t use it.

kylegalbraith··on Launch HN: Loops (YC W22) – Email for SaaS Companies
We use Loops to power some of our email things for Depot [0] and Resend for other bits of it. In general, it's been a pleasure to use.

I think there are some logic things to get right at the API level, like should I use events or contact properties to trigger loops? We're working on some of that and wish the guidance was a bit better/clearer. At the moment, any properties you send with an event get added to the contact, so it seems like contact properties are the way to go.

My last request would be to support array properties on contacts, as a given contact could be in multiple "things".

[0] https://depot.dev/

kylegalbraith··on Attention Is Off By One
I'm not an expert in whether this technique yields better or worse results. But it seems plausible that the proposal would yield a reduction in memory requirements and thus beneficial.

But in terms of a written piece of technical content, this is brilliantly written. Easy to follow and stay engaged. Well done.

kylegalbraith··on Show HN: Open-source resume builder and parser
Seems like an awesome idea you have here. However, I uploaded my partners resume as a PDF and it didn't parse out any of the relevant details. Meaning they would pretty much need to redo the entire resume in this tool.
kylegalbraith··on How to do the thing you've been avoiding
This was a very insightful read that I think helps people think about stepping outside of their comfort zones.
kylegalbraith··on $27 PineTime smartwatch that runs open-source software
Dumb question, but how do these pair/sync back to other devices?
kylegalbraith··on Launch HN: Resend (YC W23) – Email API for developers using React
We use Resend for our transactional email at https://depot.dev after migrating away from Postmark following their acquisition. It's been awesome so far and because our app is Remix underneath the hood, it was delightfully easy to get our emails exactly how we wanted them.

The visibility into what emails have been sent, to who, and what the content was is also incredibly helpful when we are talking about transactional emails. Double bonus for being able to share that email as well.

kylegalbraith··on Build all of your Docker images concurrently from a file with bake
Author here, we discovered how much `bake` can make lives easier for folks who are already using Compose via building Depot. Happy to answer any questions, share thoughts, or learn from others that have used bake to build their Docker images.
kylegalbraith··on Launch HN: Dittofeed (YC S22) – open-source customer engagement platform
Congrats on the launch and the progress. When folks want to self-host your offering, do they want to be able to run your offering on things other than Intel CPUs? I noticed that you only build an image for Intel and not for Arm.
kylegalbraith··on Show HN: Accelerated Docker builds on your local machine with Depot (YC W23)
Hi there! Kyle here, the other half of Depot. This is correct, we have a self-hosted data plane model that larger enterprises can use if they want full control over the builders + build cache.

In that deployment model, the Depot control plane passes changes to make in the customers environment via a small agent they run in their account. Here is some docs we put together for anyone that wants to go into a bit more of the details: https://depot.dev/docs/self-hosted/architecture

kylegalbraith··on Launch HN: Depot (YC W23) – Fast Docker Builds in the Cloud
Thank you for the comment and sharing your own experience! We definitely resonate with that feeling. We were having to wait for multiple 20 minute builds at our previous job when we got tired of it and started building Depot.

We should definitely be able to help here.

kylegalbraith··on Launch HN: Depot (YC W23) – Fast Docker Builds in the Cloud
Thank you for the very kind comments! It would be really cool to do something like ctr with what we have with Depot today. Did you have a part you really enjoyed with it that would be a must have for you?
kylegalbraith··on Launch HN: Depot (YC W23) – Fast Docker Builds in the Cloud
Yup we can definitely help with this. It was one of the pain points that inspired Depot as we found that QEMU was just to slow inside of things like GitHub Actions where we wanted to build both for both architectures for local development and production.
kylegalbraith··on Launch HN: Depot (YC W23) – Fast Docker Builds in the Cloud
Hey! Thank you for sharing this feedback, it's incredibly helpful and we are so grateful for it. We thought a lot about this when we decided to add a free tier and have some different ideas on what we want to do next in this realm.

For now, if you want to sign up for our free tier we can flip your org to this type of structure you are talking about, 1 project, 1 user, first 60 build minutes free & 5 cents/minute after that.

kylegalbraith··on Launch HN: Depot (YC W23) – Fast Docker Builds in the Cloud
Hey thank you for the great question! I think the short answer is that if you already have all of this wired up in CodePipeline+CodeBuild and it works for you, then you're probably set.

But there is a few steps to get there in that setup. I believe you have to have three CodeBuild projects, one for each architecture & then the manifest merge. So it works but is a bit of config to stitch together.

With Depot, you would just install our `depot` CLI in your config and run `depot build --platform linux/amd64,linux/arm64` instead of `docker build`. We handle building the image on both architectures in parallel and can push the merged result to your registry. We can even run the builders in your own AWS account so you maintain total control of the underlying infra building your image.

We are working on other features for Depot that would go beyond the speed & multi-platform capabilities. We want to surface insights and telemetry about image builds that could help them be smaller, faster, and smarter. We are also thinking about things in the container security space such as container signing, sboms, etc. Happy to answer more questions about any of this!

kylegalbraith··on Launch HN: Depot (YC W23) – Fast Docker Builds in the Cloud
Thanks for the very kind words, we're super excited to be working with you all at Windmill!
kylegalbraith··on Launch HN: Depot (YC W23) – Fast Docker Builds in the Cloud
Hey there! I'm the other half of Depot. This is an awesome tool you have built, I have actually been looking for something like this for myself as well.

Couldn't agree more with the pain points you mention, it was the biggest things that led us to start Depot and we're really excited about what we can do next.

If you ever want to do way with your hacky build process and try out Depot, we have a free tier now.

kylegalbraith··on Show HN: Cross-Platform GitHub Action
We aren't SOC2 compliant yet, but we are planning to do that this year. Yup, you can pass `depot build --load` (the same parameters you use with buildx) and we will return the built image to you. Or you can use `--push` and we will push it up to your registry.

Here is my direct email if anyone wants to chat/learn/share more about this problem space, kyle [at] depot.dev.

kylegalbraith··on Show HN: Cross-Platform GitHub Action
This was one of the frustrations that led us to create Depot (https://depot.dev/). It's a remote Docker build service that launches Intel & Arm VMs to build native multi-platform images in parallel on native CPUs with zero emulation.

Behind the scenes we are running the same engine as Docker, BuildKit, on VMs in AWS for both architectures. We combine native architecture support with a 50GB persistent SSD cache that is automatically available across builds, so no more saving/loading cache over the network.

All those things combined makes multi-platform or Arm image builds in GitHub Actions ~15x faster using Depot (example: https://depot.dev/benchmark/temporal). And it's a one line change, swap `docker build` for `depot build` or use our `depot/build-push-action` instead of `docker/build-push-action`.

kylegalbraith··on Microsoft is preparing to add ChatGPT to Bing
This resonates with me. We have all worked with someone who is a superb bullshitter, 100% confident in their responses, yet they are completely wrong. Only now, we have codified that person into chatGPT.
kylegalbraith··on Show HN: Depot – fast, remote Docker container builds
Thank you for the question!

We don't limit concurrency on the builder VMs. When you create a project you are effectively getting a dedicated build VM with a persistent SSD cache for each architecture you want to build for. We run native BuildKit on the VM and connect your `depot build` directly to the builder instance via mTLS. So your concurrency is unlimited with Depot as well (or at least as unlimited as BuildKit will allow for).

kylegalbraith··on Show HN: Depot – fast, remote Docker container builds
Yes, you can definitely use this in your Bitbucket Pipelines. Our CLI is a drop in replacement for `docker build`. So in your pipeline you would still login to your registry with `docker login` but then you can use `depot build` with all of the same options you were using before and the build can be routed to our remote builders.

So your pipeline would effectively look like this.

    image: node:10.15.0
    pipelines:
      default:
        - step:
            script:
              - curl https://depot.dev/install-cli.sh | DEPOT_INSTALL_DIR=/usr/local/bin sh
              - npm install
              - npm test
              - docker login -u $DOCKER_HUB_USER -p $DOCKER_HUB_PASSWORD
              - depot build -t <my.container.registry.io>/<my_app>:<my_tag> . --push --project <DEPOT_PROJECT_ID> --token <DEPOT_PROJECT_TOKEN>
            services:
              - docker
Here I have used `--token` for passing in a project token to authenticate the build with your project in Depot. This can also be passed as an environment variable, `DEPOT_TOKEN`.

Edit: Formatting. Also thank you for pointing out this is an integration we are missing in our docs. We will get that added!

kylegalbraith··on Show HN: Depot – fast, remote Docker container builds
Yup the caches for each architecture are available in parallel and multiple builds for a single architecture can simultaneously use the same build machine for a single project. So we don't limit the concurrency.

I believe Cloud Build has no persistent caching so you are forced to use remote cache saving and loading. Which can incur a network latency that can slow the build to some extent. Cloud Build with Kaniko also expires the layer cache after 6 hours by default.

GitHub Actions is similar except that there is the ability to store Docker cache using GitHub's Cache API via the `cache-to=gha` and `cache-from=gha` directives. However, this has limitations like only being able to store a total cache size of 10GB per repository. You also have network latency for loading/saving that cache as well.

With Depot, the cache is kept on a persistent disk. So no need to save/load it or incur network latency doing so. It's there ready to be used by any builds that come in for the given projects.

kylegalbraith··on Show HN: Depot – fast, remote Docker container builds
Thank you for the comment and sharing your thoughts!

The first thing that comes to mind is multi-platform support. Currently, it's very slow to build multi-platform images in things like Cloud Build because you have to emulate the Arm portion of the build. We don't have timings in Cloud Build for this, but in GitHub Actions a multi-platform image build can take over an hour when building for both Intel & Arm. With Depot, those builds can take less than 5 minutes because we build the image for both architectures in parallel on native CPU architectures.

Other things where Depot might be more streamlined than Cloud Build is that persistent caching is automatic. The dedicated build machines for each architecture have persistent SSD caches attached to them, so you don't need to save/load cache in between runs, it's just there ready to be used.

kylegalbraith··on Show HN: Depot – fast, remote Docker container builds
Thank you for sharing your experience and trying Depot out!

We currently charge on a per project basis as behind the scenes we are provisioning and maintaining a VM with a persistent SSD cache for each architecture you are building for (i.e. Intel & Arm). We switched to usage based pricing before rolling Depot out to the public so you are only charged for your active projects and used build minutes in a month. So far it has seemed to be working well, but we are always open to feedback and ideas on how we can make pricing better.

We don't currently document this, and we probably should, but it's entirely possible to use a single Depot project for multiple Docker images. There is no limitation that prevents this and the only downside is you may fill up your cache space at a faster rate and get fewer hits if you have different image builds clobbering the cache.

kylegalbraith··on Show HN: Depot – fast, remote Docker container builds
Thank you for the comment! We have dealt with this problem throughout our own careers at multiple companies. We should support all of the tricks you may be doing to speed up your builds, but we hope you have to do fewer of them using Depot.
← PreviousPage 4 of 6Next →