-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Update devcontainer #37261
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Update devcontainer #37261
Conversation
devcontainer["mounts"] = [ | ||
"source=/var/run/docker.sock,target=/var/run/docker.sock,type=bind,consistency=cached", | ||
"source=${localEnv:HOME}/.ssh,target=/home/vscode/.ssh,type=bind,consistency=cached", | ||
"source=${localEnv:HOME}${localEnv:USERPROFILE}/.ssh,target=/home/vscode/.ssh,type=bind,consistency=cached", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This fallback example is also in the documentation https://containers.dev/implementors/json_reference/#variables-in-devcontainerjson
Uncompressed package size comparisonComparison with ancestor Diff per package
Decision✅ Passed |
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: 79129e1 Optimization Goals: ✅ No significant changes detected
|
perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
---|---|---|---|---|---|---|
➖ | tcp_syslog_to_blackhole | ingress throughput | +1.20 | [+1.09, +1.30] | 1 | Logs |
➖ | docker_containers_cpu | % cpu utilization | +0.39 | [-3.56, +4.34] | 1 | Logs |
➖ | quality_gate_idle | memory utilization | +0.31 | [+0.24, +0.38] | 1 | Logs bounds checks dashboard |
➖ | quality_gate_idle_all_features | memory utilization | +0.26 | [+0.17, +0.36] | 1 | Logs bounds checks dashboard |
➖ | file_tree | memory utilization | +0.15 | [+0.01, +0.30] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency | egress throughput | +0.08 | [-0.55, +0.71] | 1 | Logs |
➖ | file_to_blackhole_100ms_latency | egress throughput | +0.05 | [-0.59, +0.68] | 1 | Logs |
➖ | otlp_ingest_logs | memory utilization | +0.03 | [-0.10, +0.15] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http2 | egress throughput | +0.00 | [-0.59, +0.60] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency_linear_load | egress throughput | +0.00 | [-0.23, +0.24] | 1 | Logs |
➖ | otlp_ingest_metrics | memory utilization | -0.00 | [-0.16, +0.16] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http1 | egress throughput | -0.00 | [-0.59, +0.58] | 1 | Logs |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | -0.01 | [-0.03, +0.02] | 1 | Logs |
➖ | uds_dogstatsd_to_api | ingress throughput | -0.01 | [-0.30, +0.27] | 1 | Logs |
➖ | file_to_blackhole_300ms_latency | egress throughput | -0.02 | [-0.65, +0.61] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency | egress throughput | -0.04 | [-0.66, +0.59] | 1 | Logs |
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | -0.07 | [-0.95, +0.82] | 1 | Logs |
➖ | file_to_blackhole_500ms_latency | egress throughput | -0.08 | [-0.66, +0.50] | 1 | Logs |
➖ | ddot_metrics | memory utilization | -0.29 | [-0.41, -0.18] | 1 | Logs |
➖ | docker_containers_memory | memory utilization | -0.34 | [-0.39, -0.29] | 1 | Logs |
➖ | uds_dogstatsd_20mb_12k_contexts_20_senders | memory utilization | -0.47 | [-0.52, -0.43] | 1 | Logs |
➖ | ddot_logs | memory utilization | -0.61 | [-0.75, -0.47] | 1 | Logs |
➖ | quality_gate_logs | % cpu utilization | -4.16 | [-6.87, -1.45] | 1 | Logs bounds checks dashboard |
Bounds Checks: ✅ Passed
perf | experiment | bounds_check_name | replicates_passed | links |
---|---|---|---|---|
✅ | docker_containers_cpu | simple_check_run | 10/10 | |
✅ | docker_containers_memory | memory_usage | 10/10 | |
✅ | docker_containers_memory | simple_check_run | 10/10 | |
✅ | file_to_blackhole_0ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http1 | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http1 | memory_usage | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http2 | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http2 | memory_usage | 10/10 | |
✅ | file_to_blackhole_1000ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_1000ms_latency_linear_load | memory_usage | 10/10 | |
✅ | file_to_blackhole_100ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_100ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_300ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_300ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_500ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_500ms_latency | memory_usage | 10/10 | |
✅ | quality_gate_idle | intake_connections | 10/10 | bounds checks dashboard |
✅ | quality_gate_idle | memory_usage | 10/10 | bounds checks dashboard |
✅ | quality_gate_idle_all_features | intake_connections | 10/10 | bounds checks dashboard |
✅ | quality_gate_idle_all_features | memory_usage | 10/10 | bounds checks dashboard |
✅ | quality_gate_logs | intake_connections | 10/10 | bounds checks dashboard |
✅ | quality_gate_logs | lost_bytes | 10/10 | bounds checks dashboard |
✅ | quality_gate_logs | memory_usage | 10/10 | bounds checks dashboard |
Explanation
Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%
Performance changes are noted in the perf column of each table:
- ✅ = significantly better comparison variant performance
- ❌ = significantly worse comparison variant performance
- ➖ = no significant change in performance
A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".
For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:
-
Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.
-
Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.
-
Its configuration does not mark it "erratic".
CI Pass/Fail Decision
✅ Passed. All Quality Gates passed.
- quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
Static quality checks✅ Please find below the results from static quality gates Successful checksInfo
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello 👋 It would be great to add some tests to verify that the devcontainer continues to work across the following use cases:
- Using the
devcontainer
commands.- Functionality with IDEs (Visual Studio Code, Jetbrains).
- Using
skaffold
commands.
Having these tests is important to avoid regressions for developers relying on the devcontainer for their work with the Datadog Agent.
Tests occurred in a separate PR as planned #37438 |
@@ -23,7 +23,7 @@ | |||
DEVCONTAINER_DIR = ".devcontainer" | |||
DEVCONTAINER_FILE = "devcontainer.json" | |||
DEVCONTAINER_NAME = "datadog_agent_devcontainer" | |||
DEVCONTAINER_IMAGE = "registry.ddbuild.io/ci/datadog-agent-devenv:1-arm64" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are we still getting arm64 tag?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Multiarch image now https://hub.docker.com/r/datadog/agent-dev-env-linux/tags
@@ -93,10 +96,9 @@ def setup( | |||
"datadog_agent_devcontainer", | |||
] | |||
devcontainer["features"] = {} | |||
devcontainer["remoteUser"] = "datadog" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this change mean that we now need root
privileges to build the agent?
The previous commit illustrates what choosing the user would look like and must be used on this branch that modifies the developer image: DataDog/datadog-agent-buildimages@main...ofek/user This strategy will not work so I am instead allocating my time on making our tooling replacing and satisfying the core functionality of the |
What does this PR do?
datadog/agent-dev-env-linux
found here: https://github.com/DataDog/datadog-agent-buildimages/tree/main/dev-envs/linuxMotivation
Consolidate developer images to only one per platform
Describe how you validated your changes
Example run: https://github.com/DataDog/datadog-agent/actions/runs/15308606394
And locally: