overleaf / overleaf/toolkit

[Loongarch64] no matching manifest for linux/loong64 in the manifest list entries

Open
#331 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
1.3k
Forks
310
Avg merge
3d 12h
Merged PRs (30d)
1

Description

I'm trying to deploy local overleaf on a Loongson-3A5000 machine, for which's CPU architecture is loongarch64.

While mongo pulling the docker file, it says:

resbi@la464v:/home/resbi/Gits/overleaf-toolkit git:(master) $ sudo ./bin/up
Initiating Mongo replica set...
[+] Running 0/1
 ⠼ mongo Pulling                                                                                                  29.4s
no matching manifest for linux/loong64 in the manifest list entries

I know it means there is no image built for loongarch64, so I'm now deploying overleaf on a x86_64 machine.

If I really want to deploy overleaf on a loongarch64 machine, instead of creating a x86_64 virtual machine on it, is there any possibility to build an image for that architecture myself?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the ./bin/up entry point and the Mongo image configuration involved in the reported pull. Check the image manifest and the project's documented image-building process for linux/loong64; done would mean a documented or supported path to run the Mongo dependency on that architecture.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, shell
Domain
devops
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.