-
Notifications
You must be signed in to change notification settings - Fork 4
Use dev-container image #45
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?
Changes from all commits
6c6be8f
8d9f6fe
5800432
73e5bb6
fe93834
d193ee9
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -25,7 +25,7 @@ jobs: | |
| e2e: | ||
| runs-on: ubuntu-latest | ||
| container: | ||
| image: ghcr.io/vdaas/vald/vald-ci-container:nightly | ||
| image: ghcr.io/vdaas/vald/vald-dev-container:nightly | ||
| options: "--add-host host.docker.internal:host-gateway" | ||
| steps: | ||
| - uses: actions/checkout@v3 | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🧩 Analysis chain🏁 Script executed: #!/bin/bash
set -euo pipefail
# Verify no deprecated checkout major versions remain in workflows.
rg -nP 'uses:\s*actions/checkout@v[123]\b' .github/workflowsRepository: vdaas/vald-client-python Length of output: 131 🌐 Web query:
💡 Result: actions/checkout@v3 is not formally deprecated or scheduled for support end in 2025. It uses Node 16 runtime, which reached end-of-life in GitHub Actions runners on November 12, 2024. Using v3 now produces deprecation warnings due to Node 16, and workflows may fail if runners no longer support it post-EOL. Official docs and changelog recommend upgrading to v4 (Node 20), v5 (Node 24), or latest v6 for continued support and security updates. No specific 2025 cutoff for v3 is announced; older major versions receive security fixes indefinitely per GitHub policy. Upgrade to actions/checkout@v6 (latest as of 2026-01-09) to avoid issues. Citations:
🏁 Script executed: #!/bin/bash
# Examine the full e2e.yaml workflow to verify claims in scratchpad
head -50 .github/workflows/e2e.yaml | cat -nRepository: vdaas/vald-client-python Length of output: 1370 🏁 Script executed: #!/bin/bash
# Check all GitHub workflow files for action versions and permissions
echo "=== Checking for permissions block in e2e.yaml ==="
grep -n "permissions:" .github/workflows/e2e.yaml || echo "No permissions block found"
echo -e "\n=== Full workflow structure (first 40 lines) ==="
cat -n .github/workflows/e2e.yaml | head -40Repository: vdaas/vald-client-python Length of output: 1498 Upgrade Line 31 uses Proposed fix- - uses: actions/checkout@v4
+ - uses: actions/checkout@v4🧰 Tools🪛 actionlint (1.7.12)[error] 31-31: the runner of "actions/checkout@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue (action) 🤖 Prompt for AI Agents |
||
|
|
||
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.
🧩 Analysis chain
🏁 Script executed:
cat -n .github/workflows/e2e.yaml | head -40Repository: vdaas/vald-client-python
Length of output: 1370
🏁 Script executed:
Repository: vdaas/vald-client-python
Length of output: 50
🏁 Script executed:
Repository: vdaas/vald-client-python
Length of output: 52
🏁 Script executed:
Repository: vdaas/vald-client-python
Length of output: 93
🏁 Script executed:
Repository: vdaas/vald-client-python
Length of output: 50
🏁 Script executed:
Repository: vdaas/vald-client-python
Length of output: 50
🏁 Script executed:
Repository: vdaas/vald-client-python
Length of output: 50
🏁 Script executed:
# Check if there's a .github directory structure ls -la .github/workflows/Repository: vdaas/vald-client-python
Length of output: 559
🏁 Script executed:
Repository: vdaas/vald-client-python
Length of output: 50
🏁 Script executed:
Repository: vdaas/vald-client-python
Length of output: 93
🏁 Script executed:
# Look at the actual content of the e2e.yaml more carefully cat .github/workflows/e2e.yamlRepository: vdaas/vald-client-python
Length of output: 1125
🏁 Script executed:
Repository: vdaas/vald-client-python
Length of output: 92
🏁 Script executed:
Repository: vdaas/vald-client-python
Length of output: 50
🏁 Script executed:
Repository: vdaas/vald-client-python
Length of output: 705
🏁 Script executed:
Repository: vdaas/vald-client-python
Length of output: 52
🏁 Script executed:
Repository: vdaas/vald-client-python
Length of output: 50
🏁 Script executed:
Repository: vdaas/vald-client-python
Length of output: 52
🏁 Script executed:
Repository: vdaas/vald-client-python
Length of output: 2114
🏁 Script executed:
Repository: vdaas/vald-client-python
Length of output: 52
🏁 Script executed:
Repository: vdaas/vald-client-python
Length of output: 2191
🏁 Script executed:
Repository: vdaas/vald-client-python
Length of output: 52
🏁 Script executed:
Repository: vdaas/vald-client-python
Length of output: 1034
🏁 Script executed:
Repository: vdaas/vald-client-python
Length of output: 128
🏁 Script executed:
# Search web for information about vald-dev-container nightly tag web_search ghcr.io vdaas vald-dev-container nightly digest pinningRepository: vdaas/vald-client-python
Length of output: 164
🌐 Web query:
vdaas vald-dev-container nightly image digest pinning GitHub Actions💡 Result:
The vdaas/vald-dev-container is a nightly-built Docker image used for development containers (devcontainers) in the Vald project (github.com/vdaas/vald). It is built via GitHub Actions workflow .github/workflows/dockers-dev-container-image.yaml on pushes to main (nightly tag) and PRs (pr-XXXX tags). Images are published to Docker Hub (hub.docker.com/r/vdaas/vald-dev-container) and GHCR. No evidence of digest pinning (e.g., image:tag@sha256:digest) in workflows or devcontainer.json for this image or its base images. Workflows use tag references like :nightly or :pr-XXXX. Docker Hub lists digests (e.g., sha256:8d544902cc0a for pr-3493), but they are not pinned in configs. General pinning best practices apply (e.g., result 2 recommends digest pinning for security), but Vald workflows do not implement it for vald-dev-container. Devcontainer.json likely references "vdaas/vald-dev-container:nightly" by tag.
Citations:
Coordinate with vdaas/vald-client-ci to pin container image by digest.
Line 28 uses
:nightly, a mutable tag that rebuilds daily and can cause non-deterministic E2E results. However, this file is marked "DO NOT EDIT" and auto-synced from vdaas/vald-client-ci. The fix should be coordinated at the source (vdaas/vald-client-ci level) or the nightly build process should support stable digest references. Pinning locally may be overwritten on next sync.🤖 Prompt for AI Agents