tarikrital
(Tarik from Nearmelab)
May 17, 2025, 11:33am
1
Context:
Fedora Linux host, SQL Server in Docker (mcr.microsoft.com/mssql/server:2022-latest).
Works: DBeaver connects to localhost,1433 with SA credentials.
Fails: Umbraco installer (same credentials) throws connection errors.
Tried:
Connection strings: localhost,1433 / container_name,1433 / host.docker.internal.
TrustServerCertificate=True.
Question:
What’s the correct host value for Umbraco’s installer when SQL runs in Docker? Is there a hidden Umbraco-specific gotcha?
sebastiaan
(Sebastiaan Janssen âš“)
May 17, 2025, 3:27pm
2
You will need to give some more context, how is your docker setup, is SQL server in it’s own container, how is the docker networking set up etc.
tarikrital
(Tarik from Nearmelab)
May 17, 2025, 5:09pm
3
Thanks for your response. Here’s my setup:
SQL Server : Running in its own Docker container (mcr.microsoft.com/mssql/server:2022-latest).
Umbraco : Currently on my Fedora host (not containerized).
Networking : Default Docker bridge.
I resolved it by using 172.17.0.1 (bridge) in Umbraco’s server.
1 Like
sebastiaan
(Sebastiaan Janssen âš“)
May 18, 2025, 10:53am
4
As I understand it your can name your running docker containers (docker run --name sqlserver) and then you should be able to connect to Server=sqlserver instead of having to rely on an IP address that might change.
If you were to dockerize your Umbraco install, it needs to be in a docker network (docker network create my-network) and then you specify that network, something like: docker run --network my-network - that way you can connect between containers.
1 Like
tarikrital
(Tarik from Nearmelab)
May 19, 2025, 8:30am
5
connect to Server=sqlserver instead of having to rely on an IP address that might change.
Correct I should consider that when using docker because it is more reliable.
Thanks
system
(system)
Closed
June 18, 2025, 8:31am
6
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.