Open ondreju93 opened 6 years ago
Hi, any chance of someone taking a look at this? Our CI tests against mssql are taking 6-7 minutes and I believe I can cut that in half if I could use tmpfs.
The same here. Any chances that it will be fixed soon?
I got around it by a hacky script that creates a 2GB loopback device in memory
dd if=/dev/zero of=/opt/jetbrains/teamcity-mssql-tmpfs/mssql1.img bs=1M count=2048
losetup /dev/loop1 /opt/jetbrains/teamcity-mssql-tmpfs/mssql1.img
mkfs.ext4 /dev/loop1
rm -rf /opt/jetbrains/teamcity-mssql-data1
mkdir /opt/jetbrains/teamcity-mssql-data1
mount /dev/loop1 /opt/jetbrains/teamcity-mssql-data1
chown -R teamcity:teamcity /opt/jetbrains/teamcity-mssql-data1
And the following in the docker-compose.yml
volumes:
- /opt/jetbrains/teamcity-mssql-data1:/var/opt/mssql/data
Saw nearly 6-8x the speed of tests in our test runner when using the above vs. running it on a M.2 SSD. We use it for a test runner (so it's all under jetbrains/teamcity directories) but feel free to stick it wherever on your filesystem.
Bump. Facing the same issue !
Related : #110
When mounting /var/opt/mssql to a tmpfs, i got the following errors:
I am runnning the container like that:
docker run -d -e 'ACCEPT_EULA=Y' -e 'SA_PASSWORD=password' -p 1433:1433 --tmpfs /var/opt/mssql:rw --name mssql -v /my-path-to-init-scripts:/import microsoft/mssql-server-linux /import/init.sh
In my case init script does a very basic setup:
and init-sql.sql basically creates and sets up a default user for my application