#Kubernetes in docker for mac container exec_start container exec_die how to
Sqlcmd -S localhost,1433 -U sa -Q $QUERY -P let’s check to see if our database is there and tpcc100 is in there! sqlcmd -S localhost,1433 -U sa -Q 'SELECT name from sys.databases' -P If you’re copying a backup into a container to restore you can use this same technique to set permissions on the backup file so SQL Server has access to read the file.So, if you are new to Docker, you might wonder how to run a docker container. QUERY="CREATE DATABASE tpcc100 ON (FILENAME = '/var/opt/mssql/data/tpcc100.mdf'), (FILENAME = '/var/opt/mssql/data/tpcc_log100.ldf') FOR ATTACH " With everything set properly, let’s attach the database. docker exec sql1 bash -c 'ls -laR /var/opt/mssql/data/tpcc*' These permissions enable the mssql user to read and write these files. The user and group owners of the files are now mssql and root and the permissions are rw for each file. docker exec -u 0 sql1 bash -c 'chmod 660 /var/opt/mssql/data/tpcc*' Here we’re going to set the permissions to rw using the octal notation of 660 for both the user and group owner.
The second command we’ll need is chmod to set the permissions on the files. docker exec -u 0 sql1 bash -c 'chown 10001:0 /var/opt/mssql/data/tpcc*' The first command run is chown, which sets the user and group owner as mssql, UID 10001 inside the container, and GID 0, which is the root user. Since the container is running as mssql we need to specify the -u 0 parameter to run these commands as root.
We’ll use docker exec to run the appropriate commands inside the container to set the ownership and permissions. So let’s fix things up and set the appropriate owners and permissions on the files. Set the appropriate owners and permissions on the database files in the container docker exec sql1 bash -c 'ls -lan /var/opt/mssql/data/tpcc*' These files are not accessible by SQL Server since the UID of user mssql is 10001. So those are the permissions on the files copied into the container. I’m on a Mac and my current user’s UID is 501 and GID is 20. In the directory listing below, for the files that we copied in, you can see the UID is 501 and the GID is 20. So let’s look at things file ownership and permissions using the -n parameter on the ls command. The human-readable names are just for us humans.
In Linux, UID and GID are used for permissions. So we need to look at things using the UID and GID. The user accounts and groups on the base OS likely don’t sync up with the user accounts and groups inside the container. When using docker cp to copy files into a container, the UID and GID of the user executing the copy are used as the default permission set on the files copied into the container. docker cp tpcc100.mdf sql1:/var/opt/mssql/data/ĭocker cp tpcc100_log.ldf sql1:/var/opt/mssql/data/Įxamine the ownership and permissions after copying the file into the container Next, let’s use docker cp to copy an existing database, both the data and log files, into the container. Uid=10001(mssql) gid=0(root) groups=0(root)Ĭopy the database files into the container The UID for mssql is 10001 and the user is a member of the root group, GID 0. We can use the id command to look at the UID and GID information for a user. USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND First, using ps -aux, in the output below, you can see the sqlservr processes are running as the user mssql. With the container up and running, let’s check out a few things. Here’s we’re starting up SQL Server 2019 CU11 and attaching a Docker data volume for our persistent data. Start up a containerįirst up, let’s start up a container. The appropriate permissions on files are needed, so the SQL Server process has the proper access to any database files, log files, and backup files. The SQL Server process sqlservr running in containers runs as the non-privileged user mssql. This post will walk you through setting file permissions on database files copied into a container.
0 kommentar(er)
