


Gorm application cannot connect to PostgreSQL in docker container on Mac, ignoring DSN
php editor Xiaoxin recently encountered a problem, which is a connection problem when using the Gorm application on Mac to connect to PostgreSQL in a docker container. The specific performance is that the DSN is ignored. DSN is the abbreviation of data source name and is used to specify database connection information. This problem annoys me to no end because not being able to connect to the database will cause the application to not run properly. Next, I will share the problems I encountered and the solutions, hoping to help everyone.
Question content
I try to create a simple go rest api. I am using gorm library for database processing but it cannot connect to the database in the container. I think this might be an issue with docker on the apple chip, but not sure. I have another project that uses basically the same setup but has absolutely no issues connecting to the database.
Basically, the connection parameters seem to change completely at runtime, ignoring the dsn string
This is docker-compose.yml
:
version: '3' services: db: image: 'postgres:latest' container_name: bazos-watcher-db ports: - '5420:5432' volumes: - dbdata:/var/lib/postgresql/data - ./scripts/init.sql:/docker-entrypoint-initdb.d/init.sql env_file: - 'docker.env' restart: always volumes: dbdata:
This is the part that makes the database connection:
dsn := "bazos:kokos@tcp(localhost:5420)/bazos?charset=utf8mb4&parsetime=true&loc=local" dbopen, err := gorm.open(postgres.open(dsn), &gorm.config{})
dsn parameter matches the parameters configured in docker.env
. pgadmin has no problem establishing the connection.
This is the error I'm getting, for some reason the connection parameters seem to have changed completely:
[error] failed to initialize database, got error failed to connect to `host=/private/tmp user=tassilo database=`: dial error (dial unix /private/tmp/.s.PGSQL.5432: connect: no such file or directory) 2023/03/15 17:20:59 failed to connect to `host=/private/tmp user=tassilo database=`: dial error (dial unix /private/tmp/.s.PGSQL.5432: connect: no such file or directory) exit status 1
I tried changing the last part of the dsn string and deleting and recreating the container, but still no success.
Solution
I naively assumed that the dsn string was in the same format as mysql. Instead, it should look like this:
dsn := "host=localhost user=gorm password=gorm dbname=gorm port=9920 sslmode=disable TimeZone=Asia/Shanghai"
The above is the detailed content of Gorm application cannot connect to PostgreSQL in docker container on Mac, ignoring DSN. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



OpenSSL, as an open source library widely used in secure communications, provides encryption algorithms, keys and certificate management functions. However, there are some known security vulnerabilities in its historical version, some of which are extremely harmful. This article will focus on common vulnerabilities and response measures for OpenSSL in Debian systems. DebianOpenSSL known vulnerabilities: OpenSSL has experienced several serious vulnerabilities, such as: Heart Bleeding Vulnerability (CVE-2014-0160): This vulnerability affects OpenSSL 1.0.1 to 1.0.1f and 1.0.2 to 1.0.2 beta versions. An attacker can use this vulnerability to unauthorized read sensitive information on the server, including encryption keys, etc.

The article explains how to use the pprof tool for analyzing Go performance, including enabling profiling, collecting data, and identifying common bottlenecks like CPU and memory issues.Character count: 159

Queue threading problem in Go crawler Colly explores the problem of using the Colly crawler library in Go language, developers often encounter problems with threads and request queues. �...

The article discusses writing unit tests in Go, covering best practices, mocking techniques, and tools for efficient test management.

The library used for floating-point number operation in Go language introduces how to ensure the accuracy is...

Backend learning path: The exploration journey from front-end to back-end As a back-end beginner who transforms from front-end development, you already have the foundation of nodejs,...

The article discusses managing Go module dependencies via go.mod, covering specification, updates, and conflict resolution. It emphasizes best practices like semantic versioning and regular updates.

Under the BeegoORM framework, how to specify the database associated with the model? Many Beego projects require multiple databases to be operated simultaneously. When using Beego...
