-
Notifications
You must be signed in to change notification settings - Fork 748
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
Building the mssql-server-windows-developer dockerfile fails #420
Comments
After more digging, seems my issue is related to hcsshim #152. |
Hi, Have you tried with the microsoft/mssql-server-windows-developer image. This image is compatible with Windows Server 2016 (Core, with Desktop) and Windows 10 (Professional, Enterprise - Anniversary Edition) OS Hosts. Please refer to microsoft/mssql-server-windows-developer. |
@forkazmoden, not to be rude but it doesn't seem like you read my post at all. From my initial description I'm trying to modify the microsoft/mssql-server-windows-developer image to add Full Text Search. If I could directly use the image, I would save myself the trouble of modifying it, but they have only included the base engine with the install. |
@ducttapecoder-vt did you find a solution? I'm running into the same issue trying to build a modified image of microsoft/mssql-server-windows-developer on Windows 10, with docker-desktop. Update |
In my case it ended up being a bug with the docker hcshim and virtual
memory. Reducing the memory used on my system (down from 6gb to 4gb on an
8gb system) and playing with the -m parameter (e.g. "-m 2GB") on docker
build helped finally resolve the issue.
I found out that memory management between the various isolation types
(LCOW, hyper-v, and process) are quite different and have special
considerations. Hyper-v isolation (default for Win 10) defaults to only 1GB
of memory for containers which is quite low for SQL Server and the CU13
update failed due to OOM. Combined with the memory bug, a slow HDD, and
being new to docker and getting some of the docker file changes wrong made
it a bad time. Best of luck to you.
…On Tue, May 14, 2019, 6:27 PM SubjectiveReality ***@***.***> wrote:
@ducttapecoder-vt <https://github.com/ducttapecoder-vt> did you find a
solution? I'm running into the same issue trying to build a modified image
of microsoft/mssql-server-windows-developer on Windows 10, with
docker-desktop.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#420?email_source=notifications&email_token=AJBTD6W7SD65WWMFVPK7GUTPVM4EJA5CNFSM4GWU5I6KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVM7CEA#issuecomment-492433680>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AJBTD6QGO2K2PC4VIKE3QULPVM4EJANCNFSM4GWU5I6A>
.
|
Interesting information, thank you! I edited my comment above as I found my solution. |
Long story short, I'm new to docker and trying to add Full Text Search (FTS) to the windows SQL developer image and it's not working.
Docker 2.0.0.2 30215. Engine 18.09.1
Windows 10 1809
I've tried rebuilding the developer image to add FTS a lot of different times and different ways from different machines (All windows 10) and I'm at a loss. My primary dev machine is disconnected from the internet so I had copied the exe and box files and added in the needed COPY commands. I had issues with setup.exe not being recognized as a command (like this ) and lots of other silly things. The setup.exe usually rejects the /configurationfile=configuration.ini option. Most variations, if I get it to build at all, I end up with an image that fails to run. The container says "created" for all eternity (I just terminated one that said "created 10 days ago" and was still in the "Created" state) and forces me to restart the docker service as 'stop', 'kill', and 'rm' all fail.
I reached one point where I got a 'out of memory exception' and I discovered the distinction between hyper-v (windows 10) and process isolation (server) and the 1GB RAM limit on Hyper-V. I started using -m 4GB which helped some.
One time after that I was able to get the FTS and CU13 installed but I had stripped out the CMD commands. I then tried a FROM on that image with the CMD and got the 'forever created, never started' (FCNS) containers again.
I tried recreating the successful image and adding the CMD and other items I had stripped out but got more FCNS containers.
I also tried setting a FROM the existing developer image and running setup to add FTS but no dice there either.
I finally gave up and put docker on an internet machine and tried the dockerfile verbatim and it still failed. I ran it again and got a different error! I'm pretty sure I'm not insane (I hope) so something must be wrong with docker right?
The most recent time, it failed on step 9/12 with:
The time before that:
How do I even begin troubleshooting a generic timeout? Why am I getting so many FCNS containers?
P.S. When docker 18.09.1 released, I tried doing process isolation with servercore:1809 but it said my OS didn't match (duh, but I thought the Windows 10 1809 kernel matched the server 2016 1809 kernel and that was sufficient?). I could try a Windows 10 container but that seems completely pointless. I'm working towards a Server 2016 VM to test this on, but it should work from Windows 10!
The text was updated successfully, but these errors were encountered: