-
Notifications
You must be signed in to change notification settings - Fork 107
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
Unable to build images with Microsoft SQL client packages - cannot pass environment variables or respond to prompts #3940
Comments
@achilleas-k and @richm and I discussed this on slack a bit today. One idea is to add the ability to include environmental variables with the packages. eg. [[packages]]
name = "mssql-tools"
version = "*"
environment = ["ACCEPT_EULA=y"] It's not a great idea, it requires plumbing this down through all the layers to the rpm stage in osbuild. But I don't really see any better way. Limiting it to the specific package would prevent the environment accidentally leaking into other packages and possibly causing problems. Another alternative is that |
We've asked MS about this idea. No reply yet.
Just for my info, why not |
Just a policy thing. Happy to revisit it if needed. |
No, I'm sure you have your reasons. I was just curious. |
Describe the bug
Some of the Microsoft SQL client packages require the user to accept the EULA before or during installation, either by setting an environment variable (
ACCEPT_EULA=y
), or by the package interactively prompting the user on the terminal. For example:The problem is that the image builder does not have a way to pass such environment variables through to the package manager, or deal with such interactive prompts.
Environment
/etc/os-release
and/etc/redhat-release
): anyrpm -qi osbuild-composer)
: anyTo Reproduce
Steps to reproduce the behavior:
Configure the Microsoft SQL server repositories (however repositories are configured):
Configure the list of packages to be installed:
The image build will fail
Expected behavior
Image building will succeed
Additional context
The text was updated successfully, but these errors were encountered: