Update docs content from https://github.com/depot/app

Author: nagypeterjob

content/cli/reference.mdx

@@ -665,7 +665,7 @@ Additional flags that can be used with this command.
 
 ### `depot pull-token`
 
-Generate a short-lived token to pull an image from the Depot Registry.
+Generate a short-lived token (valid for 1 hour) to pull an image from the Depot Registry.
 
 **Example**
 

content/container-builds/troubleshooting.mdx

@@ -161,6 +161,27 @@ If you're hitting Docker Hub rate limits, you can authenticate with a Docker Hub
 
 To authenticate, create a Docker Hub account if you don't have one, then set up authentication in your build environment.
 
+## Error: `failed to load ref`
+
+If you encounter a warning during container builds similar to:
+
+```text
+ERROR: failed to load ref: 05e0j9uordhz0b72g9h3e32an: not found
+```
+
+This error indicates that BuildKit couldn't find a cached layer that it expected to exist. While this appears as an error in the logs, BuildKit typically recovers by rebuilding the missing layer, so your build should still complete successfully.
+
+### How to resolve
+
+If you observe this warning frequently, increase the cache storage allocation:
+
+1. Log in to your [Depot Dashboard](https://depot.dev).
+2. Select the project and click **Settings**.
+3. Increase one or both of **Cache Storage Policy** and **Cache Retention Policy** values.
+4. Monitor your builds to verify if the fix worked.
+
+If you continue to see this warning after adjusting your cache settings, [reach out to support](/help) with your project ID and build details.
+
 ## Error: `.git directory not found in build context`
 
 When using Depot's `build-push-action` for Docker builds, you might encounter an error such as:
@@ -207,6 +228,35 @@ For more information, refer to the [Docker documentation on keeping the git dire
 
 If you continue to see git-related errors after adding this build argument, verify that your checkout step is fetching the necessary git history and [reach out to support](/help) if needed.
 
+## Error: `cannot merge resource due to conflicting Schema URL`
+
+When running `depot build` or `depot bake`, you may encounter an error message like:
+
+```text
+Error: cannot merge resource due to conflicting Schema URL
+```
+
+This error is typically caused by conflicting OpenTelemetry (OTEL) environment variables set in your local build environment. These environment variables can interfere with Depot's internal telemetry system.
+
+### How to resolve
+
+Set the environment variable `DEPOT_DISABLE_OTEL=1` in your environment before running `depot build`. This variable disables the embedded OpenTelemetry tracing in Depot CLI. Use this to prevent conflicts when your environment has existing OpenTelemetry instrumentation:
+
+```bash
+export DEPOT_DISABLE_OTEL=1
+depot build .
+```
+
+Alternatively, you can set it inline with your build command:
+
+```bash
+DEPOT_DISABLE_OTEL=1 depot build .
+```
+
+If you're using a CI/CD environment, add `DEPOT_DISABLE_OTEL=1` to your environment variables for the build step.
+
+If the error persists after setting this environment variable, [reach out to support](/help) with your project ID and build details.
+
 ## Error: `remote error: tls: bad record MAC`
 
 When building container images, you may encounter an error like:
@@ -231,9 +281,28 @@ This error is typically caused by network instability on the client side. Check
 
 If you continue experiencing connection issues from your local machine, consider triggering builds from a CI platform instead. CI environments typically have more stable network connections and are better suited for running longer builds. See our [CI integration guides](/docs/container-builds/quickstart#continuous-integration) for setup instructions.
 
+## Error: `timed out connecting to machine: failed to create temp file`
+
+When running a build with Depot CLI, you may encounter an error similar to:
+
+```text
+Error: timed out connecting to machine: failed to create temp file: open /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/depot-cert4068571078: permission denied
+```
+
+This error indicates that Depot CLI is unable to write the TLS certificate file to a temporary directory on your local machine. The client-side TLS certificate is required to establish secure communication with the remote build server.
+
+### How to resolve
+
+- Try restarting your terminal session
+- Check available disk space on your local machine
+- Verify your user has write permissions to the directory shown in the error message
+- If using an antivirus or other security software, check if it's blocking file operations on the temporary directory
+
+If the issue persists, [reach out to support](/help) with your OS version and any security software you're running.
+
 ## Build hangs or builder won't start
 
-If your build is hung or a builder isn't coming online to serve build requests, this may be caused by:
+If your build hangs or a builder isn't coming online to serve build requests, this may be caused by:
 
 - A deadlock in BuildKit
 - A builder that isn't coming online to serve the build request

content/faq.mdx

@@ -138,3 +138,11 @@ Our high-performance caching system is automatically integrated with our GitHub
 ### How can I track usage of Depot's GitHub Actions runners?
 
 We provide detailed usage analytics for GitHub Actions inside of your Organization Usage page. You can track minutes used, job durations, and other metrics across your entire organization.
+
+### Can I use custom runner images with pre-installed software?
+
+Yes, custom runner AMIs with pre-installed software are available on the Business plan. This is useful if you need specific tools, dependencies, or configurations that aren't included in our standard runner images.
+
+With a custom runner AMI, we maintain a separate image specifically for your organization with your required software pre-installed. This can significantly reduce workflow execution time for dependencies that take time to install.
+
+To request a custom runner AMI, please [contact our team](mailto:[email protected]) with details about your requirements.

content/github-actions/overview.mdx

@@ -50,6 +50,10 @@ We track builds by the second and only bill for whole minutes used at the end of
 
 We can run our optimized runners in our cloud or your AWS account for additional security and compliance. We also support dedicated infrastructure and VPC peering options for something more custom to your needs.
 
+### Custom runner images
+
+For Business plan customers, we can create custom runner AMIs with pre-installed software tailored to your specific requirements. This is useful if you need specific tools, dependencies, or configurations that aren't included in our standard runner images. Contact us at [[email protected]](mailto:[email protected]) to discuss your needs.
+
 ### Integrates with Docker image builds
 
 If you use Depot for faster Docker image builds via our [remote container builds](/docs/container-builds/overview), your BuildKit builder runs right next to your managed GitHub Action runner, allowing for faster CI builds by mimizing network latency and data transfer.

content/github-actions/runner-types.mdx

@@ -105,7 +105,7 @@ The following labels are available:
 
 ## macOS runners
 
-macOS runners use instances with M2 chips running macOS 14 or macOS 15. Their EBS volume is provisioned with 8000 IOPS and 1000 MB/s throughput. Like the Linux runners, the macOS runners also have a disk accelerator.
+macOS runners use instances with M2 chips running macOS 14 or macOS 15. Their EBS volume is provisioned with 12000 IOPS and 1000 MB/s throughput. Like the Linux runners, the macOS runners also have a disk accelerator.
 
 The following labels are available:
 
@@ -137,3 +137,13 @@ If you'd like to see what tools and software are installed in each runner image,
 - [`depot-windows-2022`](https://github.com/actions/runner-images/blob/main/images/windows/Windows2022-Readme.md)
 
 _Note: We do our best to keep our images in sync with GitHub's, but there may be a slight delay between when GitHub updates their images and when we update ours. If you need a specific version of a tool or software, please check the links above to see if it's available in the image you're using._
+
+## Custom runner images
+
+If you need specific software pre-installed that isn't included in our standard runner images, custom runner AMIs are available on the Business plan. This is particularly useful for:
+
+- Large dependencies that take significant time to install
+- Proprietary software or custom configurations
+- Corporate security or compliance tools
+
+Contact us at [[email protected]](mailto:[email protected]) to discuss custom runner image requirements.

content/registry/overview.mdx

@@ -39,7 +39,7 @@ The Depot Registry supports authentication using various types of Depot tokens.
 - **Project tokens** - Full push and pull permissions for the specific project they're associated with
 - **Organization tokens** - Full push and pull permissions for any project within the organization
 - **Trust relationship tokens** - Full push and pull permissions for the project when issued via OIDC trust relationships
-- **Pull tokens** - Read-only access for pulling images only (generated via `depot pull-token`)
+- **Pull tokens** - Read-only access for pulling images only, valid for 1 hour (generated via `depot pull-token`)
 
 ### Authentication for `docker` CLI