-
Notifications
You must be signed in to change notification settings - Fork 33
[WIP] Fix cicd image build path for lxd-initializer image #248
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: spectro-master
Are you sure you want to change the base?
Changes from all commits
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 | ||||||
|---|---|---|---|---|---|---|---|---|
|
|
@@ -29,32 +29,29 @@ spec: | |||||||
| effect: "NoSchedule" | ||||||||
| initContainers: | ||||||||
| - name: ensure-lxd | ||||||||
| image: ubuntu:22.04 | ||||||||
| image: us-east1-docker.pkg.dev/spectro-images/cluster-api/lxd-initializer:v0.6.1-spectro-4.7.13 | ||||||||
|
||||||||
| image: us-east1-docker.pkg.dev/spectro-images/cluster-api/lxd-initializer:v0.6.1-spectro-4.7.13 | |
| image: {{ .Values.image.repository }}:{{ .Values.image.tag }} |
Copilot
AI
Sep 18, 2025
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.
The repeated nsenter -t 1 -m -p -- sh -c 'command -v apt-get >/dev/null 2>&1 && pattern creates code duplication. Consider extracting this into a shell function or combining the commands into a single nsenter call.
| nsenter -t 1 -m -p -- sh -c 'command -v apt-get >/dev/null 2>&1 && apt-get update || true' | |
| nsenter -t 1 -m -p -- sh -c 'command -v apt-get >/dev/null 2>&1 && apt-get install -y snapd systemd || true' | |
| nsenter -t 1 -m -p -- sh -c 'if command -v apt-get >/dev/null 2>&1; then apt-get update && apt-get install -y snapd systemd; fi || true' |
This file was deleted.
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.
The variable name should not have quotes around the string value. In Makefiles, quotes are literal and will be included in the variable value, which could cause issues when the variable is used in commands.