You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
dockerIssues related to our docker files and docker scriptsjenkinsIssues that enhance or fix our jenkins servermacosIssues that affect or relate to the MAC OSz-linuxIssues that affect or relate to the s390x LINUX OS
The current process has a number of things which are not ideal and should be fixed:
The RHEL support should be in the Tools.gmk file alongside CentOS, Fedora and Oracle Linux. If it can pull from the default location from yum reinstall --downloadonly to source the rpms (since the yum command requires root access even to only perform the download)
Is the current process for distributing the devkit (Manually copying it onto the machine that runs rhel7_docker_image_updater in /usr/local) the best approach? Probably not ...
Verify the tarball before installing it
Adjust podman use to have --userns=keep-id for the bind volume mapping in the future Comment ref
The text was updated successfully, but these errors were encountered:
github-actionsbot
added
docker
Issues related to our docker files and docker scripts
macos
Issues that affect or relate to the MAC OS
z-linux
Issues that affect or relate to the s390x LINUX OS
jenkins
Issues that enhance or fix our jenkins server
labels
Apr 4, 2024
dockerIssues related to our docker files and docker scriptsjenkinsIssues that enhance or fix our jenkins servermacosIssues that affect or relate to the MAC OSz-linuxIssues that affect or relate to the s390x LINUX OS
Follow on to #3700
The current process has a number of things which are not ideal and should be fixed:
yum reinstall --downloadonly
to source the rpms (since theyum
command requires root access even to only perform the download)--userns=keep-id
for the bind volume mapping in the future Comment refThe text was updated successfully, but these errors were encountered: