Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

no matching manifest for linux/arm64/v8 in the manifest list entries #63

Closed
Aopenz opened this issue Apr 24, 2023 · 13 comments
Closed

no matching manifest for linux/arm64/v8 in the manifest list entries #63

Aopenz opened this issue Apr 24, 2023 · 13 comments
Labels
closed | duplicate This issue or pull request already exists.

Comments

@Aopenz
Copy link

Aopenz commented Apr 24, 2023

no matching manifest for linux/arm64/v8 in the manifest list entries

@Josh-XT
Copy link
Owner

Josh-XT commented Apr 24, 2023

Can you be more descriptive about what your machine is running and when you're getting this error?

@Josh-XT Josh-XT added type | report | incompatibility Incompatibility with an expectedly compatible suite (OS, tool, browser, etc). reply needed | waiting for response Waiting for more info from the creator of the issue. If not responded to in a week, may be closed. labels Apr 24, 2023
@Aopenz
Copy link
Author

Aopenz commented Apr 24, 2023

This problem has been solved. But I test, this system can no longer run properly on MAC M2, the front section and back end are normal after running open https://127.0.0.1:3000 or other addresses, keep showing network errors, can not load out the correct page.

@Josh-XT
Copy link
Owner

Josh-XT commented Apr 24, 2023

This problem has been solved. But I test, this system can no longer run properly on MAC M2, the front section and back end are normal after running open https://127.0.0.1:3000 or other addresses, keep showing network errors, can not load out the correct page.

It is not at HTTPS, it is http://localhost

@Aopenz
Copy link
Author

Aopenz commented Apr 24, 2023

sorry,Input error, it is http://localhost ,but the web keep showing network errors

@Josh-XT
Copy link
Owner

Josh-XT commented Apr 24, 2023

Please run:

docker-compose ps

To see if your containers are running.

@Aopenz
Copy link
Author

Aopenz commented Apr 24, 2023

NAME IMAGE COMMAND SERVICE CREATED STATUS PORTS
agent-llm-backend-1 ghcr.io/josh-xt/agent-llm-backend:v1.0.6 "uvicorn app:app --h…" backend About a minute ago Up About a minute 5000/tcp, 0.0.0.0:5001->5001/tcp
agent-llm-frontend-1 ghcr.io/josh-xt/agent-llm-frontend:v1.0.6 "docker-entrypoint.s…" frontend About a minute ago Up About a minute 0.0.0.0:80->3000/tcp

@Josh-XT
Copy link
Owner

Josh-XT commented Apr 24, 2023

You changed the port to 5001, so the front end has no idea where the back end is.

@Aopenz
Copy link
Author

Aopenz commented Apr 24, 2023

when i use the port 5000:[+] Running 0/0
⠋ Container agent-llm-backend-1 Start... 0.0s
Error response from daemon: Ports are not available: exposing port TCP 0.0.0.0:5000 -> 0.0.0.0:0: listen tcp 0.0.0.0:5000: bind: address already in use

@Josh-XT
Copy link
Owner

Josh-XT commented Apr 24, 2023

Are you using the docker-compose for mac?

@Aopenz
Copy link
Author

Aopenz commented Apr 24, 2023

yes

@Josh-XT
Copy link
Owner

Josh-XT commented Apr 24, 2023

when i use the port 5000:[+] Running 0/0 ⠋ Container agent-llm-backend-1 Start... 0.0s Error response from daemon: Ports are not available: exposing port TCP 0.0.0.0:5000 -> 0.0.0.0:0: listen tcp 0.0.0.0:5000: bind: address already in use

Sorry missed earlier you said this was Mac. I just merged something that should fix that. You'll need to do this first:

docker-compose down
docker-compose -f docker-compose-mac.yml down

Then do:

docker-compose -f docker-compose-mac.yml up --build -d

@Josh-XT
Copy link
Owner

Josh-XT commented Apr 24, 2023

Please continue this conversation in #61 if you're still having issues. We have some more information over there and there is a lot of overlap with this issue.

@Josh-XT Josh-XT closed this as completed Apr 24, 2023
@Josh-XT Josh-XT added closed | duplicate This issue or pull request already exists. and removed type | report | incompatibility Incompatibility with an expectedly compatible suite (OS, tool, browser, etc). reply needed | waiting for response Waiting for more info from the creator of the issue. If not responded to in a week, may be closed. labels Apr 24, 2023
@Aopenz
Copy link
Author

Aopenz commented Apr 24, 2023

=> ERROR [base 7/12] RUN pip install --no-cache-dir -r requirements-mac 1.7s

[base 7/12] RUN pip install --no-cache-dir -r requirements-mac.txt:
#0 0.269 ERROR: Could not open requirements file: [Errno 2] No such file or directory: 'requirements-mac.txt'


failed to solve: executor failed running [/bin/sh -c pip install --no-cache-dir -r requirements-mac.txt]: exit code: 1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed | duplicate This issue or pull request already exists.
Projects
None yet
Development

No branches or pull requests

2 participants