TroubleshootingOfficial documentation9 min readIssue list

FastGPT Images and architecture Issue List

Find 13 FastGPT image and architecture troubleshooting articles, with checks for image tags, downloads, CPU compatibility, and startup errors.

This page collects the 13 published documents about container images and processor architecture, grouped by symptom, so a document can be found directly from what the error looks like.

Three symptoms that belong to this stage

  1. An image fails to pull or the tag does not match the expected version
  2. The processor architecture does not match the image
  3. A native dependency fails to load on a particular architecture

If none of the three match, go back to the deployment and environment issue landscape and narrow down again.

The general order for this stage

  1. Take the full error from the backend service log for this stage's component, including the component name and error code
  2. Verify from inside the deployment that the component can be reached on its own, ruling out network and permission causes
  3. Check the component version against the main service version
  4. Follow the entry below whose symptom is closest, then repeat the same operation to verify

Published documents (13)

DocumentArea
Configure and Use FastGPT Dataset Image Searchtutorial
Deploy ChatGLM2-M3E Custom Model Image for FastGPTdeploy
FastGPT 4.14.7 Self-Hosted Platform Improvementsdeploy
FastGPT 4.15.0 Platform Technical Improvementsdeploy
FastGPT 4.15.05 Core Platform Improvementsdeploy
FastGPT Dataset Vector Storage Architecture Overviewtutorial
Run Initialization for FastGPT After Image Upgradedeploy
Test FastGPT App Chat and Image Recognition with SiliconClouddeploy
Update FastGPT 4.15.0 Service Imagesdeploy
Update FastGPT 4.15.0-beta6 Container Imagesdeploy
Update FastGPT Application Images on Sealosdeploy
Update FastGPT Container Image Tags for v4.15.0deploy
Update FastGPT Service Images for v4.16.0-beta1 Upgradedeploy

What this list does not cover

Entries cover cases that can be reproduced publicly, grouped by symptom. The following need separate confirmation:

  • A symptom caused by several factors at once, which needs the order above to rule them out one by one
  • The same symptom caused by configuration specific to the commercial edition
  • Cases coupled to a particular infrastructure environment that cannot be reproduced in a standard deployment

Keep reading

References

If the problem is still not located

The entries above cover cases that can be reproduced from public information. If the problem depends on configuration details of a specific deployment, or needs runtime logs to confirm, contact sales for deployment-stage support; the cloud service can be used directly without handling environment dependencies.

  • Contact sales: support for self-hosting and upgrades
  • Get started: use the cloud service and skip environment setup
  • Pricing: compare what the cloud and self-hosted forms cover