Subnet name broken after migration to docker container

未关闭
  • 哪里不对？
#4,620 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
45/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
冷清
技术栈
php
领域
database

调研方向

No files or tests are identified in the issue. Start by comparing the automatic migration and the documented MySQL/MariaDB import paths, and request the Docker Compose configuration and relevant database details to narrow down the cause. Done means subnet names display correctly after importing the dump into the Docker deployment.

由索引模型根据 Issue 内容生成。

描述

Hi, I imported an SQL dump from a server currently running phpIPAM v1.5.0 into a new server with a docker container running the same phpIPAM version.

Steps followed:

  1. Followed the official guide to get the dump: https://phpipam.net/news/migrate-phpipam-to-new-server/
  2. Uploaded MIGRATE.sql to phpipam/db inside the web container.
  3. To import, I followed the automatic migration/DB creation. (MIGRATE.sql was detected successfully).

Apparently eveything goes well but after logging in, subnets appear like this:

Image

I also tried with the option "MySQL/MariaDB import instructions" but the result is the same.

Please let know if you need any more info like docker compose.

主要语言
PHP
星标
2.8k
派生
800
平均合并
10 分钟
30 天内合并 PR
1

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

phpipam/phpipam 的其他 Issue

查看 phpipam/phpipam 的全部 Issue

相似的 Issue

更多 PHP Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。