Share via

Trying to install and run Azure SQL Edge on Docker on Mac (intel). Runs for a few seconds and then stops.

Sunraj sharma 65 Reputation points
2023-09-23T18:02:21.3366667+00:00

Overview

  1. I am trying to install and run SQL server from Docker.
  2. It runs for a few seconds and then exits with a code of 255.
  3. I am trying to install Azure SQL edge on Macbook running on intel.

Commands I ran to install the image

sudo docker pull mcr.microsoft.com/azure-sql-edge

Command to install docker

Command I used to run the container

docker run -e "ACCEPT_EULA=1" -e "MSSQL_SA_PASSWORD=password123" -e "MSSQL_PID=Developer" -e "MSSQL_USER=SA" -p 1433:1433 -d --name=sql mcr.microsoft.com/azure-sql-edge

Error starts

  1. The container runs for a few seconds, and then shuts down with an Exit status of 255.
  2. Complete log is pasted below, but i am guessing this might be a reason for the error? enter image description here

Logs

sunraj@Sunrajs-MacBook-Pro ~ % docker logs sql 
                                           
Azure SQL Edge will run as non-root by default.
This container is running as user mssql.
To learn more visit https://go.microsoft.com/fwlink/?linkid=2140520.
2023/09/23 17:36:55 [launchpadd] INFO: Extensibility Log Header: <timestamp> <process> <sandboxId> <sessionId> <message>
2023/09/23 17:36:55 [launchpadd] WARNING: Failed to load /var/opt/mssql/mssql.conf ini file with error open /var/opt/mssql/mssql.conf: no such file or directory
2023/09/23 17:36:55 [launchpadd] ERROR: RevoScaleR installation was not found. RevoScaleR is required to be installed in order to use R scripts.
2023/09/23 17:36:55 [launchpadd] ERROR: revoscalepy installation was not found. revoscalepy is required to be installed in order to use Python scripts.
2023/09/23 17:36:55 [launchpadd] INFO: DataDirectories =  /bin:/etc:/lib:/lib32:/lib64:/sbin:/usr/bin:/usr/include:/usr/lib:/usr/lib32:/usr/lib64:/usr/libexec/gcc:/usr/sbin:/usr/share:/var/lib:/opt/microsoft:/opt/mssql-extensibility:/opt/mssql/mlservices:/opt/mssql/lib/zulu-jre-11:/opt/mssql-tools
2023/09/23 17:36:55 Drop permitted effective capabilities.
2023/09/23 17:36:55 [launchpadd] INFO: Polybase remote hadoop bridge disabled
2023/09/23 17:36:55 [launchpadd] INFO: Launchpadd is connecting to mssql on localhost:1431
2023/09/23 17:36:55 [launchpadd] WARNING: Failed to connect to SQL because: dial tcp 127.0.0.1:1431: getsockopt: connection refused, will reattempt connection.
2023/09/23 17:36:56 [launchpadd] WARNING: Failed to connect to SQL because: dial tcp 127.0.0.1:1431: getsockopt: connection refused, will reattempt connection.
2023/09/23 17:36:57 [launchpadd] WARNING: Failed to connect to SQL because: dial tcp 127.0.0.1:1431: getsockopt: connection refused, will reattempt connection.
2023/09/23 17:36:58 [launchpadd] WARNING: Failed to connect to SQL because: dial tcp 127.0.0.1:1431: getsockopt: connection refused, will reattempt connection.
2023-09-23 17:36:59.79 Server      The licensing PID was successfully processed. The new edition is [Azure SQL Edge Developer].
2023/09/23 17:36:59 [launchpadd] WARNING: Failed to connect to SQL because: dial tcp 127.0.0.1:1431: getsockopt: connection refused, will reattempt connection.
2023-09-23 17:36:59.98 Server      Setup step is copying system data file 'C:\templatedata\master.mdf' to '/var/opt/mssql/data/master.mdf'.
2023-09-23 17:37:00.00 Server      Did not find an existing master data file /var/opt/mssql/data/master.mdf, copying the missing default master and other system database files. If you have moved the database location, but not moved the database files, startup may fail. To repair: shutdown SQL Server, move the master database to configured location, and restart.
2023-09-23 17:37:00.01 Server      Setup step is copying system data file 'C:\templatedata\mastlog.ldf' to '/var/opt/mssql/data/mastlog.ldf'.
2023-09-23 17:37:00.01 Server      Setup step is copying system data file 'C:\templatedata\model.mdf' to '/var/opt/mssql/data/model.mdf'.
2023-09-23 17:37:00.04 Server      Setup step is copying system data file 'C:\templatedata\modellog.ldf' to '/var/opt/mssql/data/modellog.ldf'.
2023-09-23 17:37:00.07 Server      Setup step is copying system data file 'C:\templatedata\msdbdata.mdf' to '/var/opt/mssql/data/msdbdata.mdf'.
2023-09-23 17:37:00.12 Server      Setup step is copying system data file 'C:\templatedata\msdblog.ldf' to '/var/opt/mssql/data/msdblog.ldf'.
2023-09-23 17:37:00.12 Server      Setup step is copying system data file 'C:\templatedata\model_replicatedmaster.mdf' to '/var/opt/mssql/data/model_replicatedmaster.mdf'.
2023-09-23 17:37:00.14 Server      Setup step is copying system data file 'C:\templatedata\model_replicatedmaster.ldf' to '/var/opt/mssql/data/model_replicatedmaster.ldf'.
2023-09-23 17:37:00.14 Server      Setup step is copying system data file 'C:\templatedata\model_msdbdata.mdf' to '/var/opt/mssql/data/model_msdbdata.mdf'.
2023-09-23 17:37:00.19 Server      Setup step is copying system data file 'C:\templatedata\model_msdblog.ldf' to '/var/opt/mssql/data/model_msdblog.ldf'.
2023-09-23 17:37:00.22 Server      Microsoft Azure SQL Edge Developer (RTM) - 16.0.5100.7245 (X64) 
	Jun 13 2023 12:34:33 
	Copyright (C) 2022 Microsoft Corporation
	Linux (Ubuntu 20.04.6 LTS) <X64>
2023-09-23 17:37:00.22 Server      UTC adjustment: 0:00
2023-09-23 17:37:00.22 Server      (c) Microsoft Corporation.
2023-09-23 17:37:00.22 Server      All rights reserved.
2023-09-23 17:37:00.22 Server      Server process ID is 352.
2023-09-23 17:37:00.23 Server      Logging SQL Server messages in file '/var/opt/mssql/log/errorlog'.
2023-09-23 17:37:00.23 Server      Registry startup parameters: 
	 -d /var/opt/mssql/data/master.mdf
	 -l /var/opt/mssql/data/mastlog.ldf
	 -e /var/opt/mssql/log/errorlog
2023-09-23 17:37:00.23 Server      SQL Server detected 1 sockets with 4 cores per socket and 4 logical processors per socket, 4 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2023-09-23 17:37:00.23 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2023-09-23 17:37:00.23 Server      Detected 3144 MB of RAM. This is an informational message; no user action is required.
2023-09-23 17:37:00.23 Server      Using conventional memory in the memory manager.
2023-09-23 17:37:00.24 Server      Detected pause instruction latency: 106 cycles.
2023-09-23 17:37:00.24 Server      Spin divider value used: 2
2023-09-23 17:37:00.24 Server      Page exclusion bitmap is enabled.
2023-09-23 17:37:00.30 Server      Buffer Pool: Allocating 524288 bytes for 432237 hashPages.
2023-09-23 17:37:00.48 Server      Buffer pool extension is already disabled. No action is necessary.
2023-09-23 17:37:00.96 Server      Installing Client TLS certificates to the store.
2023-09-23 17:37:00.97 Server      Error searching first file in /var/opt/mssql/security/ca-certificates: 3(The system cannot find the path specified.)
2023-09-23 17:37:00.97 Server      CPU vectorization level(s) detected:  SSE SSE2 SSE3 SSSE3 SSE41 SSE42 AVX AVX2 POPCNT BMI1 BMI2
2023-09-23 17:37:01.06 Server      Successfully initialized the TLS configuration. Allowed TLS protocol versions are ['1.0 1.1 1.2']. Allowed TLS ciphers are ['BLAH-BLAH-BLAH-GCM-SHA256:ECDHE-BLAH-AES256-GCM-SHA384:ECDHE-BLAH-BLAH-BLAH-SHA256:ECDHE-BLAH-BLAH-GCM-SHA384:BLAH-ECDSA-AES128-SHA256:BLAH-ECDSA-BLAH-BLAH:ECDHE-ECDSA-AES256-SHA:BLAH-ECDSA-BLAH-BLAH:BLAH-GCM-SHA384:AES128-GCM-SHA256:BLAH-BLAH:BLAH-BLAH:BLAH-SHA:AES128-SHA:!DHE-RSBLAHA-BLAH-GCM-SHA384:!DHE-RSA-AES128-GCM-SHA256:BLAH'].
2023-09-23 17:37:01.09 Server      Query Store settings initialized with enabled = 1, 
2023-09-23 17:37:01.11 Server      Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2023-09-23 17:37:01.13 Server      Using dynamic lock allocation.  Initial allocation of 500 Lock blocks and 1000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
2023-09-23 17:37:01.14 Server      Database Instant File Initialization: enabled. For security and performance considerations see the topic 'Database Instant File Initialization' in SQL Server Books Online. This is an informational message only. No user action is required.
ForceFlush is enabled for this instance. 
2023-09-23 17:37:01.19 Server      Total Log Writer threads: 1, Node CPUs: 2, Nodes: 1, Log Writer threads per CPU: 1, Log Writer threads per Node: 2
2023-09-23 17:37:01.20 Server      clflushopt is selected for pmem flush operation.
2023-09-23 17:37:01.22 Server      Software Usage Metrics is disabled.
2023-09-23 17:37:01.29 spid9s      [1]. Feature Status: PVS: 0. CTR: 0. ConcurrentPFSUpdate: 1. ConcurrentGAMUpdate: 0. ConcurrentSGAMUpdate: 0, CleanupUnderUserTransaction: 0. TranLevelPVS: 0
2023-09-23 17:37:01.31 spid9s      Starting up database 'master'.
ForceFlush feature is enabled for log durability.
2023-09-23 17:37:01.37 spid9s      The tail of the log for database master is being rewritten to match the new sector size of 4096 bytes.  2560 bytes at offset 398848 in file /var/opt/mssql/data/mastlog.ldf will be written.
2023-09-23 17:37:01.44 spid9s      Converting database 'master' from version 927 to the current version 964.
2023-09-23 17:37:01.44 spid9s      Database 'master' running the upgrade step from version 927 to version 928.
2023-09-23 17:37:01.47 spid9s      Database 'master' running the upgrade step from version 928 to version 929.
2023-09-23 17:37:01.50 spid9s      Database 'master' running the upgrade step from version 929 to version 930.
2023-09-23 17:37:01.51 spid9s      Database 'master' running the upgrade step from version 930 to version 931.
2023-09-23 17:37:01.51 spid9s      Database 'master' running the upgrade step from version 931 to version 932.
2023-09-23 17:37:01.52 spid9s      Database 'master' running the upgrade step from version 932 to version 933.
2023-09-23 17:37:01.53 spid9s      Database 'master' running the upgrade step from version 933 to version 934.
2023-09-23 17:37:01.53 spid9s      Database 'master' running the upgrade step from version 934 to version 935.
2023-09-23 17:37:01.55 spid9s      Database 'master' running the upgrade step from version 935 to version 936.
2023-09-23 17:37:01.55 spid9s      Database 'master' running the upgrade step from version 936 to version 937.
2023-09-23 17:37:01.56 spid9s      Database 'master' running the upgrade step from version 937 to version 938.
2023-09-23 17:37:01.57 spid9s      Database 'master' running the upgrade step from version 938 to version 939.
2023-09-23 17:37:01.57 spid9s      Database 'master' running the upgrade step from version 939 to version 940.
2023-09-23 17:37:01.58 spid9s      Database 'master' running the upgrade step from version 940 to version 941.
2023-09-23 17:37:01.58 spid9s      Database 'master' running the upgrade step from version 941 to version 942.
2023-09-23 17:37:01.59 spid9s      Database 'master' running the upgrade step from version 942 to version 943.
2023-09-23 17:37:01.61 spid9s      Database 'master' running the upgrade step from version 943 to version 944.
2023-09-23 17:37:01.62 spid9s      Database 'master' running the upgrade step from version 944 to version 945.
2023-09-23 17:37:01.63 spid9s      Database 'master' running the upgrade step from version 945 to version 946.
2023-09-23 17:37:01.64 spid9s      Database 'master' running the upgrade step from version 946 to version 947.
2023-09-23 17:37:01.64 spid9s      Database 'master' running the upgrade step from version 947 to version 948.
2023-09-23 17:37:01.65 spid9s      Database 'master' running the upgrade step from version 948 to version 949.
2023-09-23 17:37:01.66 spid9s      Database 'master' running the upgrade step from version 949 to version 950.
2023-09-23 17:37:01.66 spid9s      Database 'master' running the upgrade step from version 950 to version 951.
2023-09-23 17:37:01.68 spid9s      Database 'master' running the upgrade step from version 951 to version 952.
2023-09-23 17:37:01.68 spid9s      Database 'master' running the upgrade step from version 952 to version 953.
2023-09-23 17:37:01.69 spid9s      Database 'master' running the upgrade step from version 953 to version 954.
2023-09-23 17:37:01.70 spid9s      Database 'master' running the upgrade step from version 954 to version 955.
2023-09-23 17:37:01.70 spid9s      Database 'master' running the upgrade step from version 955 to version 956.
2023-09-23 17:37:01.77 spid9s      Database 'master' running the upgrade step from version 956 to version 957.
2023-09-23 17:37:01.78 spid9s      Database 'master' running the upgrade step from version 957 to version 963.
2023-09-23 17:37:01.79 spid9s      Database 'master' running the upgrade step from version 963 to version 964.
2023-09-23 17:37:01.97 spid9s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2023-09-23 17:37:01.98 spid9s      [AutoStartAuditSessions] Starting audit session task
2023-09-23 17:37:01.98 spid9s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
2023-09-23 17:37:01.99 Server      External governance manager initialized
2023-09-23 17:37:01.99 spid9s      XE session 'system_health' started.
2023-09-23 17:37:02.02 spid9s      SQL Trace ID 1 was started by login "sa".
2023-09-23 17:37:02.03 spid9s      Server name is 'ec8bb361d4d3'. This is an informational message only. No user action is required.
2023-09-23 17:37:02.04 spid20s     ERROR: Unable to set system administrator password: Password validation failed. The password does not meet SQL Server password policy requirements because it is not complex enough. The password must be at least 8 characters long and contain characters from three of the following four sets: Uppercase letters, Lowercase letters, Base 10 digits, and Symbols..
2023-09-23 17:37:02.05 spid20s     An error occurred during server setup. See previous errors for more information.
2023-09-23 17:37:02.05 spid20s     SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
2023-09-23 17:37:02.06 spid23s     Password policy update was successful.
2023-09-23 17:37:02.06 spid13s     [32767]. Feature Status: PVS: 0. CTR: 0. ConcurrentPFSUpdate: 1. ConcurrentGAMUpdate: 0. ConcurrentSGAMUpdate: 0, CleanupUnderUserTransaction: 0. TranLevelPVS: 0
2023-09-23 17:37:02.07 spid9s      [4]. Feature Status: PVS: 0. CTR: 0. ConcurrentPFSUpdate: 1. ConcurrentGAMUpdate: 0. ConcurrentSGAMUpdate: 0, CleanupUnderUserTransaction: 0. TranLevelPVS: 0
2023-09-23 17:37:02.08 spid9s      Starting up database 'ms
Azure SQL Edge
Azure SQL Edge
An Azure service that provides a small-footprint, edge-optimized data engine with built-in artificial intelligence. Previously known as Azure SQL Database Edge.
49 questions
0 comments
Accepted answer
  1. ShaktiSingh-MSFT 16,086 Reputation points
    2023-09-25T06:34:47.3933333+00:00

    Hi Sunraj sharma •,

    Welcome to Microsoft Q&A forum and thanks for using Azure Services.

    As I understand, you are Trying to install and run Azure SQL Edge on Docker on Mac (intel). Runs for a few seconds and then stops.

    Let us know if we understood it otherwise.

    Thanks for sharing detailed logs.

    As per the error present in logs:

    ERROR: Unable to set system administrator password: Password validation failed. The password does not meet SQL Server password policy requirements because it is not complex enough. The password must be at least 8 characters long and contain characters from three of the following four sets: Uppercase letters, Lowercase letters, Base 10 digits, and Symbols..

    It seems that the password created for Server does not comply to the password policy stated above.

    Please retry using password combination which makes it complex enough with at least 8 characters along with other details.

    Do let us know if you still face issue after making complex password changes. Thanks

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.