Nestjs/TypeORM 无法连接到 Docker MariaDB
[英]Nestjs/TypeORM Cannot connect to Docker MariaDB
问题描述
Whenever I run my docker image containing nodejs 11.10 & mariadb, I get the following error:
每当我运行包含 nodejs 11.10 和 mariadb 的 docker 映像时，都会出现以下错误：
[Nest] 16 - 3/12/2019, 11:24:02 AM [TypeOrmModule] Unable to connect to the database.
The same issue happens when I use mysql:latest & mysql:5.6 .当我使用mysql:latest & mysql:5.6时会发生同样的问题。 This is my connection:这是我的连接：
TypeOrmModule.forRoot({
type: 'mariadb',
host: '172.17.0.1',
port: 3306,
username: 'nest',
password: 'secret',
database: 'nest',
entities: [__dirname + '/**/*.entity{.ts,.js}'],
synchronize: true,
}),
Has anyone else ever had this issue, and so, know how to fix it?有没有其他人遇到过这个问题，所以，知道如何解决它？ Thanks!谢谢！
2 个解决方案
解决方案1
1 已采纳 2019-03-12 12:18:02
This problem occurs because of entities: [__dirname + '/**/*.entity{.ts,.js}'], .出现此问题的原因是entities: [__dirname + '/**/*.entity{.ts,.js}'], . Because __dirname does somehow not resolve to your projects directory but '' instead, it will try to scan your whole drive for entities and obviously does not have the permissions to do so.因为__dirname以某种方式不会解析到您的项目目录而是'' ，它会尝试扫描您的整个驱动器以查找实体，并且显然没有这样做的权限。
Workaround解决方法
Instead of scanning for entities, list them explicitly:与其扫描实体，不如明确列出它们：
entities: [UserEntity, ProductEntity],
If you are using webpack for hmr, you can also try the following config to resolve __dirname correctly:如果你在 hmr 中使用 webpack，你也可以尝试以下配置来正确解析__dirname ：
webpack.config.js：
node: { __dirname: false, },
解决方案2
0 2020-03-26 07:19:56
This helped me out:这帮助了我：
entities: [__dirname + '/../**/*.entity{.ts,.js}']
Note the starting path '/../' mean start scanning from absolute path.注意起始路径'/../'表示从绝对路径开始扫描。
声明:本站的技术帖子网页，遵循CC BY-SA 4.0协议，如果您需要转载，请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.