在1panel中能否指定外部postgresql数据库

我有一个postgresqlsql数据库,但是部署maxkb的时候我不想再开一个postgresqlsql数据库,那样运维起来太麻烦了,有没有什么办法在1panel中指定外部的数据库连接呢,或者需要在docker-compose配置什么变量才能够实现这个功能?
麻烦恢复以下喽,谢谢

如果是通过离线安装包部署,可以在部署前修改install.conf文件中的参数进行配置。

如果是通过1panel部署呢,有没有通过指定环境变量的方式来指定外部数据库?

1Panel部署不方便修改,仅仅能修改一个docker-compose文件,开放的配置有限,如果使用外部数据库,建议使用离线部署方式,可以修改数据库连接配置。

现象

现在使用离线部署方式使用外部数据库部署目前无法启动,数据库链接正常,也看到31个表了但是无法访问,容器一直在重启。

版本信息

maxkb:v1.10.1-lts
postgresql:PostgreSQL 16.0 (Debian 16.0-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit

日志信息

/opt/maxkb/logs/max_kb.log

2025-02-24 21:03:32 [schema DEBUG] CREATE TABLE “embedding” (“id” varchar(128) NOT NULL PRIMARY KEY, “source_id” varchar(128) NOT NULL, “source_type” varchar(5) NOT NULL, “is_active” boolean NOT NULL, “embedding” vector NOT NULL, “meta” jsonb NOT NULL, “dataset_id” uuid NOT NULL, “document_id” uuid NOT NULL, “paragraph_id” uuid NOT NULL); (params None)

一直在重复这一句
drf_exception.log 与unexpected_exception.log为空,无内容

数据库表信息

django_migrations
system_setting
user
team
team_member
team_member_permission
model
problem
dataset
document
paragraph
problem_paragraph_mapping
application_chat
application
application_dataset_mapping
django_content_type
application_api_key
application_chat_record
application_public_access_client
application_work_flow_version
application_access_token
image
file
django_apscheduler_djangojob
django_celery_beat_periodictasks
django_apscheduler_djangojobexecution
django_celery_beat_crontabschedule
django_celery_beat_intervalschedule
django_celery_beat_solarschedule
django_celery_beat_clockedschedule
django_celery_beat_periodictask

运行状态信息

可以用docker logs -f maxkb --tail 200看一下实时日志。

日志如下

  Applying embedding.0001_initial...Building prefix dict from the default dictionary ...
DEBUG:jieba:Building prefix dict from the default dictionary ...
Loading model from cache /tmp/jieba.cache
DEBUG:jieba:Loading model from cache /tmp/jieba.cache
Loading model cost 0.745 seconds.
DEBUG:jieba:Loading model cost 0.745 seconds.
Prefix dict has been built successfully.
DEBUG:jieba:Prefix dict has been built successfully.
Operations to perform:
  Apply all migrations: application, contenttypes, dataset, django_apscheduler, django_celery_beat, embedding, function_lib, setting, users
Running migrations:
2025-02-25 11:04:57 [schema DEBUG] CREATE TABLE "embedding" ("id" varchar(128) NOT NULL PRIMARY KEY, "source_id" varchar(128) NOT NULL, "source_type" varchar(5) NOT NULL, "is_active" boolean NOT NULL, "embedding" vector NOT NULL, "meta" jsonb NOT NULL, "dataset_id" uuid NOT NULL, "document_id" uuid NOT NULL, "paragraph_id" uuid NOT NULL); (params None)
ERROR:root:Perform migrate failed, exit
Traceback (most recent call last):
  File "/opt/py3/lib/python3.11/site-packages/django/db/backends/utils.py", line 87, in _execute
    return self.cursor.execute(sql)
           ^^^^^^^^^^^^^^^^^^^^^^^^
psycopg2.errors.UndefinedObject: 错误:  类型 "vector" 不存在
LINE 1: ...T NULL, "is_active" boolean NOT NULL, "embedding" vector NOT...
                                                             ^


The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/opt/maxkb/app/main.py", line 40, in perform_db_migrate
    management.call_command('migrate')
  File "/opt/py3/lib/python3.11/site-packages/django/core/management/__init__.py", line 194, in call_command
    return command.execute(*args, **defaults)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/py3/lib/python3.11/site-packages/django/core/management/base.py", line 458, in execute
    output = self.handle(*args, **options)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/py3/lib/python3.11/site-packages/django/core/management/base.py", line 106, in wrapper
    res = handle_func(*args, **kwargs)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/py3/lib/python3.11/site-packages/django/core/management/commands/migrate.py", line 356, in handle
    post_migrate_state = executor.migrate(
                         ^^^^^^^^^^^^^^^^^
  File "/opt/py3/lib/python3.11/site-packages/django/db/migrations/executor.py", line 135, in migrate
    state = self._migrate_all_forwards(
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/py3/lib/python3.11/site-packages/django/db/migrations/executor.py", line 167, in _migrate_all_forwards
    state = self.apply_migration(
            ^^^^^^^^^^^^^^^^^^^^^
  File "/opt/py3/lib/python3.11/site-packages/django/db/migrations/executor.py", line 252, in apply_migration
    state = migration.apply(state, schema_editor)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/py3/lib/python3.11/site-packages/django/db/migrations/migration.py", line 132, in apply
    operation.database_forwards(
  File "/opt/py3/lib/python3.11/site-packages/django/db/migrations/operations/models.py", line 96, in database_forwards
    schema_editor.create_model(model)
  File "/opt/py3/lib/python3.11/site-packages/django/db/backends/base/schema.py", line 451, in create_model
    self.execute(sql, params or None)
  File "/opt/py3/lib/python3.11/site-packages/django/db/backends/postgresql/schema.py", line 45, in execute
    return super().execute(sql, params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/py3/lib/python3.11/site-packages/django/db/backends/base/schema.py", line 201, in execute
    cursor.execute(sql, params)
  File "/opt/py3/lib/python3.11/site-packages/django/db/backends/utils.py", line 67, in execute
    return self._execute_with_wrappers(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/py3/lib/python3.11/site-packages/django/db/backends/utils.py", line 80, in _execute_with_wrappers
    return executor(sql, params, many, context)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/py3/lib/python3.11/site-packages/django/db/backends/utils.py", line 84, in _execute
    with self.db.wrap_database_errors:
  File "/opt/py3/lib/python3.11/site-packages/django/db/utils.py", line 91, in __exit__
    raise dj_exc_value.with_traceback(traceback) from exc_value
  File "/opt/py3/lib/python3.11/site-packages/django/db/backends/utils.py", line 87, in _execute
    return self.cursor.execute(sql)
           ^^^^^^^^^^^^^^^^^^^^^^^^
django.db.utils.ProgrammingError: 错误:  类型 "vector" 不存在
LINE 1: ...T NULL, "is_active" boolean NOT NULL, "embedding" vector NOT...
                                                             ^

看起来你的pgsql没有安装vector插件,参考这个帖子看看。

OK,解决了

1 个赞