forked from blooop/devlaunch
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy path.dockerignore
More file actions
48 lines (46 loc) · 2.49 KB
/
Copy path.dockerignore
File metadata and controls
48 lines (46 loc) · 2.49 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
# Nothing in this repository builds with the root as its context any more, so
# this file is a safety net rather than a live constraint: .devcontainer's build
# was the only such build, and its `context` is now `.devcontainer` (see the
# comment on it -- devpod's prebuild tag is a hash of the context, so a
# root-sized context meant a tag that moved on every commit and a prebuilt image
# that never matched). The patterns are kept because the failures below are real,
# they cost real time to diagnose, and the day something points a build at the
# root again is not the day to rediscover them.
#
# What follows is written as it was when the devcontainer did build from here.
#
# The devcontainer image is built with the repository root as its context and a
# Dockerfile that copies nothing out of it, so everything here is pure overhead
# -- and .pixi is worse than overhead. It holds the solved environment, half a
# gigabyte of it, including symlinks that the context hasher refuses outright:
#
# failed to compute context hash: read .pixi/envs/default/lib/icu/current: is a directory
#
# So on any checkout where the environment has been installed -- which is every
# checkout the tests have ever been run in -- building the container failed
# before it started. The environment inside the container comes from a volume
# mount and pixi.lock, never from here.
#
# At any depth, not just the root. A git worktree under .claude/worktrees/ has
# an environment of its own, and one left behind by an earlier effort put the
# very symlink named above back into the context -- so the pattern that exists
# to prevent this failure was watching one directory while the failure came
# from another.
**/.pixi/
# The cargo build directory is .pixi's story again, with a different number in
# the error. It is ~15000 files on a checkout that has built the Rust workspace
# once, and devpod's context hasher stops at 5000:
#
# failed to compute context hash: directory hash incomplete: exceeded limit of
# 5000 files (partial hash computed from first 5000 files)
#
# So `test/e2e/test_ssh_config_isolation.py`, which brings this repo up as a
# devcontainer, failed on any checkout where `cargo build` had run -- which is
# every checkout the parity gate runs in, since `rust/parity.py run` builds the
# binaries and then runs the e2e tier against them. Nothing is copied out of it,
# same as the rest of this file.
rust/target/
# Local state with the same story: never copied, and only ever slows the build.
.git/
.pytest_cache/
**/.claude/worktrees/