Running MSSQL service in Bitbucket Pipeline Edited

[Todd Schiller]

The official MSSQL Linux Server Docker image expects at least 2GB of RAM: https://hub.docker.com/r/microsoft/mssql-server-linux/

It appears the Pipelines can only allocate at most 1GB to a service, however.

While we can run tests against MSSQL in Pipelines, tests that load a large amount of data using bulk inserts result in the server terminating the connection to the client.

I suspect the service is killing the connection due to lack of memory. All subsequent connections to the service then fail with a "Login timeout expired" message. I can't verify this since no error information is appearing in the pipeline log for the service

Is there any way to relax the memory ceiling on services? It doesn't look like the memory requirement for MSSQL will be relaxed any time soon: https://github.com/Microsoft/mssql-docker/issues/91

[Matthew Hillier]

I've hit the same issue, and it looks like the SQL Server container is only ever granted 1GB memory, no matter the pipeline memory configuration. :( 

[Attila Szeremi]

Great, so how are we supposed to test things in MSSQL then if the amount of memory available to services is not enough?

[unhammer]

One workaround is to install mssql manually in the main pipeline. Probably won't work for everyone, as you'll need pipeline-specific install steps, but worked for us at least (on a debian stretch image) with some .deb-fiddling.

Relaxed memory ceiling on containers would make things a lot simpler though :-/