/admin

Docker Para Error De Socket De Mac Dentro Del Contenedor

El segundo error es causado por que el cliente de docker y el socket se. O boot2docker en el caso de Mac y Windows (requiere implementarse). Y los elementos requeridos para el contenedor de la validadora en el 5ta.

-->

APPLIES TO: SQL Server (Linux only) Azure SQL Database Azure Synapse Analytics (SQL DW) Parallel Data Warehouse

This tutorial demonstrates how to move and restore a SQL Server backup file into a SQL Server 2017 Linux container image running on Docker.

This tutorial demonstrates how to move and restore a SQL Server backup file into a SQL Server 2019 Linux container image running on Docker.

  • Pull and run the latest SQL Server Linux container image.
  • Copy the Wide World Importers database file into the container.
  • Restore the database in the container.
  • Run Transact-SQL statements to view and modify the database.
  • Backup the modified database.

Prerequisites

  • Docker Engine 1.8+ on any supported Linux distribution or Docker for Mac/Windows. For more information, see Install Docker.
  • Minimum of 2 GB of disk space
  • Minimum of 2 GB of RAM
  • System requirements for SQL Server on Linux.

Pull and run the container image

  1. Open a bash terminal on Linux/Mac or an elevated PowerShell session on Windows.

  2. Pull the SQL Server 2017 Linux container image from Docker Hub.

    Tip

    Throughout this tutorial, docker command examples are given for both the bash shell (Linux/Mac) and PowerShell (Windows).

  3. To run the container image with Docker, you can use the following command:

    This command creates a SQL Server 2017 container with the Developer edition (default). SQL Server port 1433 is exposed on the host as port 1401. The optional -v sql1data:/var/opt/mssql parameter creates a data volume container named sql1ddata. This is used to persist the data created by SQL Server.

    Important

    This example uses a data volume container within Docker. If you instead chose to map a host directory, note that there are limitations for this approach on Docker for Mac and Windows. For more information, see Configure SQL Server container images on Docker.

  4. To view your Docker containers, use the docker ps command.

  5. If the STATUS column shows a status of Up, then SQL Server is running in the container and listening on the port specified in the PORTS column. If the STATUS column for your SQL Server container shows Exited, see the Troubleshooting section of the configuration guide.

  1. Open a bash terminal on Linux/Mac or an elevated PowerShell session on Windows.

  2. Pull the SQL Server 2019 Linux container image from Docker Hub.

    Tip

    Throughout this tutorial, docker command examples are given for both the bash shell (Linux/Mac) and PowerShell (Windows).

  3. To run the container image with Docker, you can use the following command:

    This command creates a SQL Server 2019 container with the Developer edition (default). SQL Server port 1433 is exposed on the host as port 1401. The optional -v sql1data:/var/opt/mssql parameter creates a data volume container named sql1ddata. This is used to persist the data created by SQL Server.

  4. To view your Docker containers, use the docker ps command.

  5. If the STATUS column shows a status of Up, then SQL Server is running in the container and listening on the port specified in the PORTS column. If the STATUS column for your SQL Server container shows Exited, see the Troubleshooting section of the configuration guide.

Change the SA password

The SA account is a system administrator on the SQL Server instance that's created during setup. After you create your SQL Server container, the MSSQL_SA_PASSWORD environment variable you specified is discoverable by running echo $MSSQL_SA_PASSWORD in the container. For security purposes, change your SA password:

  1. Choose a strong password to use for the SA user.

  2. Use docker exec to run the sqlcmd utility to change the password through a Transact-SQL statement. Replace <YourStrong!Passw0rd> and <YourNewStrong!Passw0rd> with your own password values:

Copy a backup file into the container

This tutorial uses the Wide World Importers sample database. Use the following steps to download and copy the Wide World Importers database backup file into your SQL Server container.

  1. First, use docker exec to create a backup folder. The following command creates a /var/opt/mssql/backup directory inside the SQL Server container.

  2. Next, download the WideWorldImporters-Full.bak file to your host machine. The following commands navigate to the home/user directory and downloads the backup file as wwi.bak.

  3. Use docker cp to copy the backup file into the container in the /var/opt/mssql/backup directory.

Restore the database

The backup file is now located inside the container. Before restoring the backup, it is important to know the logical file names and file types inside the backup. The following Transact-SQL commands inspect the backup and perform the restore using sqlcmd in the container.

Tip

This tutorial uses sqlcmd inside the container, because the container comes with this tool pre-installed. However, you can also run Transact-SQL statements with other client tools outside of the container, such as Visual Studio Code or SQL Server Management Studio. To connect, use the host port that was mapped to port 1433 in the container. In this example, that is localhost,1401 on the host machine and Host_IP_Address,1401 remotely.

  1. Run sqlcmd inside the container to list out logical file names and paths inside the backup. This is done with the RESTORE FILELISTONLY Transact-SQL statement.

    You should see output similar to the following:

  2. Call the RESTORE DATABASE command to restore the database inside the container. Specify new paths for each of the files in the previous step.

    You should see output similar to the following:

Verify the restored database

Run the following query to display a list of database names in your container:

You should see WideWorldImporters in the list of databases.

Make a change

The following steps make a change in the database. Uworld usmle software for mac os x 10.

  1. Run a query to view the top 10 items in the Warehouse.StockItems table.

    You should see a list of item identifiers and names:

  2. Update the description of the first item with the following UPDATE statement:

    You should see output similar to the following text:

Create a new backup

After you've restored your database into a container, you might also want to regularly create database backups inside the running container. The steps follow a similar pattern to the previous steps but in reverse.

  1. Use the BACKUP DATABASE Transact-SQL command to create a database backup in the container. This tutorial creates a new backup file, wwi_2.bak, in the previously created /var/opt/mssql/backup directory.

    You should see output similar to the following:

  2. Next, copy the backup file out of the container and onto your host machine.

Use the persisted data

In addition to taking database backups for protecting your data, you can also use data volume containers. The beginning of this tutorial created the sql1 container with the -v sql1data:/var/opt/mssql parameter. The sql1data data volume container persists the /var/opt/mssql data even after the container is removed. The following steps completely remove the sql1 container and then create a new container, sql2, with the persisted data.

  1. Stop the sql1 container.

  2. Remove the container. This does not delete the previously created sql1data data volume container and the persisted data in it.

  3. Create a new container, sql2, and reuse the sql1data data volume container.

  4. The Wide World Importers database is now in the new container. Run a query to verify the previous change you made.

    Note

    The SA password is not the password you specified for the sql2 container, MSSQL_SA_PASSWORD=<YourStrong!Passw0rd>. All of the SQL Server data was restored from sql1, including the changed password from earlier in the tutorial. In effect, some options like this are ignored due to restoring the data in /var/opt/mssql. For this reason, the password is <YourNewStrong!Passw0rd> as shown here.

  1. Stop the sql1 container.

  2. Remove the container. This does not delete the previously created sql1data data volume container and the persisted data in it.

  3. Create a new container, sql2, and reuse the sql1data data volume container.

  4. The Wide World Importers database is now in the new container. Run a query to verify the previous change you made.

    Note

    The SA password is not the password you specified for the sql2 container, MSSQL_SA_PASSWORD=<YourStrong!Passw0rd>. All of the SQL Server data was restored from sql1, including the changed password from earlier in the tutorial. In effect, some options like this are ignored due to restoring the data in /var/opt/mssql. For this reason, the password is <YourNewStrong!Passw0rd> as shown here.

Next steps

In this tutorial, you learned how to back up a database on Windows and move it to a Linux server running SQL Server 2017. You learned how to:

In this tutorial, you learned how to back up a database on Windows and move it to a Linux server running SQL Server 2019. You learned how to:

  • Create SQL Server Linux container images.
  • Copy SQL Server database backups into a container.
  • Run Transact-SQL statements inside the container with sqlcmd.
  • Create and extract backup files from a container.
  • Use data volume containers in Docker to persist SQL Server data.

Next, review other Docker configuration and troubleshooting scenarios: