-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Added MSSQL_DB, MSSQL_USER and MSSQL_PASSWORD variables #10307
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: live
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 | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
@@ -30,6 +30,9 @@ You can use several different environment variables to configure [!INCLUDE [ssno | |||||||||||||
| | --- | --- | | ||||||||||||||
| | `ACCEPT_EULA` | Set the `ACCEPT_EULA` variable to any value to confirm your acceptance of the [End-User Licensing Agreement](https://go.microsoft.com/fwlink/?LinkId=746388). Required setting for the SQL Server image. | | ||||||||||||||
| | `MSSQL_SA_PASSWORD` | Configure the `sa` password.<br /><br />The `SA_PASSWORD` environment variable is deprecated. Use `MSSQL_SA_PASSWORD` instead. | | ||||||||||||||
| | `MSSQL_DB` | Sets the name of a database to create on container startup. | | ||||||||||||||
| | `MSSQL_USER` | If `MSSQL_DB` is set, sets the name of a non-`sa` user to create on container startup. User will be granted access rights on the `MSSQL_DB` database. If this variable is used, `MSSQL_PASSWORD` must also be set. If `MSSQL_DB` is not set, this variable is ignored. | | ||||||||||||||
| | `MSSQL_PASSWORD` | Sets the password of the user whose name is in `MSSQL_USER`. If this variable is used, `MSSQL_USER` must also be set. If `MSSQL_DB` is not set, this variable is ignored. | | ||||||||||||||
|
Comment on lines
+34
to
+35
|
||||||||||||||
| | `MSSQL_USER` | If `MSSQL_DB` is set, sets the name of a non-`sa` user to create on container startup. User will be granted access rights on the `MSSQL_DB` database. If this variable is used, `MSSQL_PASSWORD` must also be set. If `MSSQL_DB` is not set, this variable is ignored. | | |
| | `MSSQL_PASSWORD` | Sets the password of the user whose name is in `MSSQL_USER`. If this variable is used, `MSSQL_USER` must also be set. If `MSSQL_DB` is not set, this variable is ignored. | | |
| | `MSSQL_USER` | If `MSSQL_DB` is set, sets the name of a non-`sa` user to create on container startup. The user is granted access to the `MSSQL_DB` database. Requires `MSSQL_PASSWORD`. If `MSSQL_DB` isn't set, this variable is ignored. | | |
| | `MSSQL_PASSWORD` | Sets the password for the user specified in `MSSQL_USER`. Requires `MSSQL_USER`. If `MSSQL_DB` isn't set, this variable is ignored. | |
Copilot
AI
Mar 31, 2026
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.
“Sets the password of the user whose name is in MSSQL_USER” is a bit unclear; MSSQL_USER is a variable, not a container. Consider rephrasing to “...the user specified by MSSQL_USER” for clarity and consistency with the other descriptions.
| | `MSSQL_PASSWORD` | Sets the password of the user whose name is in `MSSQL_USER`. If this variable is used, `MSSQL_USER` must also be set. If `MSSQL_DB` is not set, this variable is ignored. | | |
| | `MSSQL_PASSWORD` | Sets the password of the user specified by `MSSQL_USER`. If this variable is used, `MSSQL_USER` must also be set. If `MSSQL_DB` is not set, this variable is ignored. | |
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.
These new environment variables appear to be specific to the SQL Server 2025 container image (per the PR description). As written, the table reads like a general list for all versions, which could mislead readers using 2017/2019/2022 images. Consider scoping these rows to the
>=sql-server-ver17 || >=sql-server-linux-ver17moniker range, or explicitly noting they apply only to the 2025 (and later) container images.