-
Notifications
You must be signed in to change notification settings - Fork 71
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
Unable to determine endpoint type for ppc64le agent #156
Comments
Am also running into this From ppc64le-host: $ docker pull portainer/agent
Using default tag: latest
latest: Pulling from portainer/agent
no matching manifest for linux/ppc64le in the manifest list entries From amd64-host: $ docker pull portainer/agent:linux-ppc64le >/dev/null && docker manifest inspect portainer/agent:linux-ppc64le --verbose | grep architecture
"architecture": "amd64", |
Confirming that this is till an issue:
However, specifying a version works:
This is also visible on docker-hub by the |
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Running portainer-ce on amd64 and agent 1.6.0 on ppc64le using portainer/agent:linux-ppc64le
When trying to register Agent as new Endpoint via webUI:
-ce log:
2020/09/16 17:07:13 http error: Unable to get endpoint type (err=Agent Platform Header is missing) (code=500)
Agent debug run:
docker run -ti -p 9001:9001 --network=portainer_agent_network -e AGENT_CLUSTER_ADDR=<ip> --mount type=bind,src=//var/run/docker.sock,dst=/var/run/docker.sock --mount type=bind,src=//var/lib/docker/volumes,dst=/var/lib/docker/volumes portainer/agent:linux-ppc64le --platform=ppc64le portainer/agent:linux-ppc64le
Also tried:
docker service create --name portainer_agent --network portainer_agent_network --publish mode=host,target=9001,published=9001 --mode global --mount type=bind,src=//var/run/docker.sock,dst=/var/run/docker.sock --mount type=bind,src=//var/lib/docker/volumes,dst=/var/lib/docker/volumes --no-resolve-image portainer/agent:linux-ppc64le
Without
--no-resolve-image
the service will report unsupported architecture and not start.Probable issue is that Architecture is set to
amd64
inppc64le
image?Many other amd64 agent endpoints have registered and are usable using the same method at the same instance.
The text was updated successfully, but these errors were encountered: