blocks|key|3464215|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|entityMap^0^^$0|@$1|2|3|-4|4|5|6|B|7|@]|8|@]|9|$]]]|A|$]]

SQL Server 2019 Windows containers are still in preview as of this writing. If you don't join the Early Adopter program, you can create a custom image by starting with a Windows Server Core base image and then install SQL Server 2019 (and optionally CUs) to create a custom image.
The build is most easily done on a machine with internet connectivity to pull the base OS image from the public repro. You can then copy the image to the machine without an internet connection (or push it to a local private repro) and run it from there. Alternatively, pull, save, and load the OS images (steps 6-8) and run the build on the server.
Below is an example of the general steps to do this. My appologies for the formatting. I'm mardown-challenged.
<ol>
<li>create an empty directory on your Windows machine (e.g. C:\dockerfiles)
<pre><code> MKDIR C:\dockerfiles
</code></pre>
</li>
<li>create a dockerfile in that directory with the following contents
<pre><code> #Start with a Windows Server Core base image.
 #Note that the image with tag 'latest' is pulled by default, which could be older than the actual host OS version.
 #In this case, specify the version-specific to pull a later image compatible with the host OS version.

 FROM mcr.microsoft.com/windows/servercore:2004

 #Parameters for start.ps1:
 ENV sa_password=&quot;_&quot; \
 attach_dbs=&quot;[]&quot; \
 ACCEPT_EULA=&quot;_&quot; \
 sa_password_path=&quot;C:\ProgramData\Docker\secrets\sa-password&quot;

 #set default shell to PowerShell and set preferences:
 SHELL [&quot;powershell&quot;, &quot;-Command&quot;, &quot;$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue';&quot;]

 #set current directory to root (C:\)
 WORKDIR /

 #copy SQL Server setup folder into build image for installation
 COPY setup setup

 #run setup to install
 RUN \setup\setup.exe /q /ACTION=Install /INSTANCENAME=MSSQLSERVER /FEATURES=SQLEngine /UPDATEENABLED=0 /SQLSVCACCOUNT='NT AUTHORITY\System' /SQLSYSADMINACCOUNTS='BUILTIN\ADMINISTRATORS' /TCPENABLED=1 /NPENABLED=0 /IACCEPTSQLSERVERLICENSETERMS

 #remove setup files
 RUN Remove-Item -Force -Recurse -Path 'setup'

 #create empty directory (C:\SqlFiles) for user database files
 RUN &quot;mkdir SqlFiles | Out-Null&quot;

 #stop SQL Server service, configure TCP/IP, allow SQL authentication, and set default file locations
 RUN stop-service MSSQLSERVER ; \
 set-itemproperty -path 'HKLM:\software\microsoft\microsoft sql server\mssql15.MSSQLSERVER\mssqlserver\supersocketnetlib\tcp\ipall' -name tcpdynamicports -value '' ; \
 set-itemproperty -path 'HKLM:\software\microsoft\microsoft sql server\mssql15.MSSQLSERVER\mssqlserver\supersocketnetlib\tcp\ipall' -name tcpport -value 1433 ; \
 set-itemproperty -path 'HKLM:\software\microsoft\microsoft sql server\mssql15.MSSQLSERVER\mssqlserver\' -name LoginMode -value 2 ; \
 set-itemproperty -path 'HKLM:\software\microsoft\microsoft sql server\mssql15.MSSQLSERVER\mssqlserver\' -name BackupDirectory -value 'C:\SqlFiles' ; \
 set-itemproperty -path 'HKLM:\software\microsoft\microsoft sql server\mssql15.MSSQLSERVER\mssqlserver\' -name DefaultData -value 'C:\SqlFiles' ; \
 set-itemproperty -path 'HKLM:\software\microsoft\microsoft sql server\mssql15.MSSQLSERVER\mssqlserver\' -name DefaultLog -value 'C:\SqlFiles' ;

 #set command used for container health check status
 HEALTHCHECK CMD [ &quot;sqlcmd&quot;, &quot;-Q&quot;, &quot;SELECT 1;&quot; ]

 &amp;#35;copy startup script to image
 COPY start.ps1 /

 #specify command invoked when container is run from this image
 CMD .\start -sa_password $env:sa_password -ACCEPT_EULA $env:ACCEPT_EULA -attach_dbs \&quot;$env:attach_dbs\&quot; -Verbose
</code></pre>
</li>
<li>create start.ps1 file in build directory (e.g. C:\dockerfiles\start.ps1). Below is an example script similar to the one I use.
<pre><code> # The script sets the sa password and start the SQL Service
 # Also it attaches additional database from the disk
 # The format for attach_dbs

 param(
 [Parameter(Mandatory=$false)]
 [string]$sa_password,

 [Parameter(Mandatory=$false)]
 [string]$ACCEPT_EULA,

 [Parameter(Mandatory=$false)]
 [string]$attach_dbs
 )


 if($ACCEPT_EULA -ne &quot;Y&quot;)
 {
 Write-Verbose &quot;ERROR: You must accept the End User License Agreement before this container can start.&quot;
 Write-Verbose &quot;Set the environment variable ACCEPT_EULA to 'Y' if you accept the agreement.&quot;

 exit 1
 }

 #start the service
 Write-Verbose &quot;Starting SQL Server&quot;
 Start-Service MSSQLSERVER

 if($sa_password -eq &quot;_&quot;) {
 if (Test-Path $env:sa_password_path) {
 $sa_password = Get-Content -Raw $secretPath
 }
 else {
 Write-Verbose &quot;WARN: Using default SA password, secret file not found at: $secretPath&quot;
 }
 }

 if($sa_password -ne &quot;_&quot;)
 {
 Write-Verbose &quot;Changing SA login credentials&quot;
 $sqlcmd = &quot;ALTER LOGIN sa with password=&quot; +&quot;'&quot; + $sa_password + &quot;'&quot; + &quot;;ALTER LOGIN sa ENABLE;&quot;
 &amp; sqlcmd -Q $sqlcmd
 }

 $attach_dbs_cleaned = $attach_dbs.TrimStart('\\').TrimEnd('\\')

 $dbs = $attach_dbs_cleaned | ConvertFrom-Json

 if ($null -ne $dbs -And $dbs.Length -gt 0)
 {
 Write-Verbose &quot;Attaching $($dbs.Length) database(s)&quot;

 Foreach($db in $dbs) 
 { 
 $files = @();
 Foreach($file in $db.dbFiles)
 {
 $files += &quot;(FILENAME = N'$($file)')&quot;; 
 }

 $files = $files -join &quot;,&quot;
 $sqlcmd = &quot;IF EXISTS (SELECT 1 FROM SYS.DATABASES WHERE NAME = '&quot; + $($db.dbName) + &quot;') BEGIN EXEC sp_detach_db [$($db.dbName)] END;CREATE DATABASE [$($db.dbName)] ON $($files) FOR ATTACH;&quot;

 Write-Verbose &quot;Invoke-Sqlcmd -Query $($sqlcmd)&quot;
 &amp; sqlcmd -Q $sqlcmd
 }
 }

 Write-Verbose &quot;Started SQL Server.&quot;

 Write-Verbose &quot;Changing SQL Server server name to $($env:COMPUTERNAME)&quot;
 $sqlcmd = &quot;EXEC sp_dropserver @@SERVERNAME;EXEC sp_addserver N'$env:COMPUTERNAME', 'local';&quot;
 &amp; sqlcmd -Q $sqlcmd

 Write-Verbose &quot;Restarting SQL Server.&quot;
 Stop-Service MSSQLSERVER
 Start-Service MSSQLSERVER
 Write-Verbose &quot;Restarted SQL Server.&quot;

 Write-Verbose &quot;Tailing log...&quot;
 Get-Content -Path &quot;C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\Log\ERRORLOG&quot; -Wait
</code></pre>
</li>
<li>copy files from SQL 2019 installation media to a setup subdirectory (e.g. C:\dockerfiles\setup)
</li>
<li>run docker build in the contest of the build directory (e.g. C:\dockerfiles) to build and tag the custom image
<pre><code> docker build -t mssql-2019-windows-dev-rtm-example .
</code></pre>
</li>
<li>save the image to a tar file
<pre><code> docker save --output &quot;C:\temp\mssql-2019-windows-dev-rtm-example.tar&quot; mssql-2019-windows-dev-rtm-example
</code></pre>
</li>
<li>copy the image to the Windows server
<pre><code> copy &quot;C:\temp\mssql-2019-windows-dev-rtm-example.tar&quot; &quot;\\YourServer\c$\temp\mssql-2019-windows-dev-rtm-example.tar&quot;
</code></pre>
</li>
<li>load the image from the tar file on the Windows server machine:
<pre><code> docker load --input &quot;C:\temp\mssql-2019-windows-dev-rtm-example.tar&quot;
</code></pre>
</li>
<li>example to run the image
<pre><code> docker run -d -p 14331:1433 -h sql2019 --name sql2019 -e &quot;sa_password=y0ourS@pAssword&quot; -e &quot;ACCEPT_EULA=Y&quot; -e attach_dbs=&quot;&quot; --rm mssql-2019-windows-dev-rtm-example:latest
</code></pre>
</li>
</ol>
Be aware Windows containers are not yet supported on production and you are on your own with SQL 2019 images at this time unless you join the EA preview.

I am in bit of a predicament,and would appreciate any help to move forward from my current situation
I have been given a VM running on Windows Server 2016 with Docker Enterprise installed. My management wants to have SQL Server 2019 with docker on windows containers running within this VM. This is a POC project. The VM does not have any internet connection, and therefore, I am unable to pull the base image from the docker hub. I know that there are SQL Server 2017 developer editions available. What can be done to make sure that I can go ahead with having a container in this situation? Especially when the VM does not have any internet connection?
What I tried doing was to download a SQL Server 2017 Developer edition on my local machine running Windows 10Pro, and then moved the container image onto the VM. But when I tried to load the container, I got an error message saying that &quot;Host OS does not match&quot;. That is when I found the website below
<a href="https://learn.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/version-compatibility?tabs=windows-server-2004%2Cwindows-10-2004" rel="nofollow noreferrer">https://learn.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/version-compatibility?tabs=windows-server-2004%2Cwindows-10-2004</a>
Please suggest as to how I can create an image in such a situation

Building a custom SQL Server 2017/2019 container on a windows server without internet

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我的处境有点困难，希望能帮助我摆脱目前的困境。我得到了一个运行在Windows 2016上并安装了的VM。我的管理层希望在此VM中运行带有停靠器的SQL Server 2019。这是一个POC项目。VM没有任何互联网连接，因此，我无法从码头集线器中提取基本映像。我知道有Server 2017开发人员版本可供使用。在这种情况下，怎样才能确保我能有一个容器呢？特别是当VM没有任何互联网连接的时候？我尝

问在没有internet的windows服务器上构建自定义Server 2017/2019容器
EN

回答 1

Database Administration用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在没有internet的windows服务器上构建自定义Server 2017/2019容器EN