Skip to content
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

Modify container image for bots/infrastructure migration #78

Merged
merged 7 commits into from
Nov 21, 2024

Conversation

nikolaszimmermann
Copy link
Member

Contains a few individual changes, needed for the bot/infrastructure migration.

These services would start with the container, when using systemd as
PID 1 (when not sharing the PID namespace with the host). Avoid that.
One can specify the option multiple times, to pass additional arguments
to "podman build".
Allow to override the get_sdk_images_directory(), by specifying
the WKDEV_SDK_IMAGES_DIRECTORY environment variable.
Point to webkit-container-sdk, instead of wkdev-sdk, following the
rename of the official repository name.
Copy link
Member

@TingPing TingPing left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

scripts/host-only/wkdev-sdk-bakery Show resolved Hide resolved
Comment on lines +66 to +67
for environment_variable in "${cumulated_values_env[@]}"
do
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
for environment_variable in "${cumulated_values_env[@]}"
do
for environment_variable in "${cumulated_values_env[@]}"; do

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missed that suggestion, sorry -- will fix it up later.

# systemd as PID 1 within the container (usually, we don't spawn systemd
# within the wkdev-sdk container, for interactive usage, but we do so
# when deploying the wkdev-sdk image as bot).
RUN find /etc/systemd/ -type l -name '*.service' -print -exec rm {} \;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do worry about this causing an easy to miss issue in the future, however looking at the current services there I don't think there is a problem.

Copy link
Member

@TingPing TingPing Nov 21, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also it shouldn't be a problem to actually remove things like cupsd (socket activated anyway) and pipewire from the image, we only use them as clients, if the packages allow that.

Use do use apache for some testing though.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, we can always refine. This is most likely not the last change of this kind.

@TingPing
Copy link
Member

CI fails with no space left on device (@dpino ?)

@nikolaszimmermann
Copy link
Member Author

CI fails with no space left on device (@dpino ?)

A bit ironic - that is why we moved to our own runners in the first place 😊

@nikolaszimmermann nikolaszimmermann merged commit ccd09fe into main Nov 21, 2024
1 of 2 checks passed
@nikolaszimmermann nikolaszimmermann deleted the nzimmermann/wkdev_sdk_bots branch November 21, 2024 09:25
@nikolaszimmermann
Copy link
Member Author

I manually ran podman image prune on the host that runs the gitlab-runner. Should be fine now.

@nikolaszimmermann
Copy link
Member Author

Oops, I diddn't intend to squash before merging, sorry :/

@nikolaszimmermann nikolaszimmermann self-assigned this Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants