Skip to content

Commit d14224e

Browse files
PedroGuerraPTgithub-actions[bot]
authored andcommitted
Update docs content from https://github.com/depot/app
1 parent 56a6ff7 commit d14224e

File tree

6 files changed

+45
-2
lines changed

6 files changed

+45
-2
lines changed

content/cli/reference.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -665,7 +665,7 @@ Additional flags that can be used with this command.
665665

666666
### `depot pull-token`
667667

668-
Generate a short-lived token to pull an image from the Depot Registry.
668+
Generate a short-lived token (valid for 1 hour) to pull an image from the Depot Registry.
669669

670670
**Example**
671671

content/container-builds/troubleshooting.mdx

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -161,6 +161,27 @@ If you're hitting Docker Hub rate limits, you can authenticate with a Docker Hub
161161

162162
To authenticate, create a Docker Hub account if you don't have one, then set up authentication in your build environment.
163163

164+
## Error: `failed to load ref`
165+
166+
If you encounter a warning during container builds similar to:
167+
168+
```text
169+
ERROR: failed to load ref: 05e0j9uordhz0b72g9h3e32an: not found
170+
```
171+
172+
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.
173+
174+
### How to resolve
175+
176+
If you observe this warning frequently, increase the cache storage allocation:
177+
178+
1. Log in to your [Depot Dashboard](https://depot.dev).
179+
2. Select the project and click **Settings**.
180+
3. Increase one or both of **Cache Storage Policy** and **Cache Retention Policy** values.
181+
4. Monitor your builds to verify if the fix worked.
182+
183+
If you continue to see this warning after adjusting your cache settings, [reach out to support](/help) with your project ID and build details.
184+
164185
## Error: `.git directory not found in build context`
165186

166187
When using Depot's `build-push-action` for Docker builds, you might encounter an error such as:

content/faq.mdx

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -138,3 +138,11 @@ Our high-performance caching system is automatically integrated with our GitHub
138138
### How can I track usage of Depot's GitHub Actions runners?
139139

140140
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.
141+
142+
### Can I use custom runner images with pre-installed software?
143+
144+
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.
145+
146+
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.
147+
148+
To request a custom runner AMI, please [contact our team](mailto:[email protected]) with details about your requirements.

content/github-actions/overview.mdx

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -50,6 +50,10 @@ We track builds by the second and only bill for whole minutes used at the end of
5050

5151
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.
5252

53+
### Custom runner images
54+
55+
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.
56+
5357
### Integrates with Docker image builds
5458

5559
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

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -137,3 +137,13 @@ If you'd like to see what tools and software are installed in each runner image,
137137
- [`depot-windows-2022`](https://github.com/actions/runner-images/blob/main/images/windows/Windows2022-Readme.md)
138138

139139
_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._
140+
141+
## Custom runner images
142+
143+
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:
144+
145+
- Large dependencies that take significant time to install
146+
- Proprietary software or custom configurations
147+
- Corporate security or compliance tools
148+
149+
Contact us at [[email protected]](mailto:[email protected]) to discuss custom runner image requirements.

content/registry/overview.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ The Depot Registry supports authentication using various types of Depot tokens.
3939
- **Project tokens** - Full push and pull permissions for the specific project they're associated with
4040
- **Organization tokens** - Full push and pull permissions for any project within the organization
4141
- **Trust relationship tokens** - Full push and pull permissions for the project when issued via OIDC trust relationships
42-
- **Pull tokens** - Read-only access for pulling images only (generated via `depot pull-token`)
42+
- **Pull tokens** - Read-only access for pulling images only, valid for 1 hour (generated via `depot pull-token`)
4343

4444
### Authentication for `docker` CLI
4545

0 commit comments

Comments
 (0)