arm64v8 image issues

[shandshellin]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

unable to spin up container using :latest image for arm64v8. Can someone provide a specific tage to a known working imager version for amr64?

Expected Behavior

Should determine the correct architecture automatically and grab the image.

Steps To Reproduce

1. create service using :latest image
2. watch it fail repeatedly

Environment

- OS: Debian
- How docker service was installed: installed in the usual way as per the docker page, works for every other arm64 image i use

CPU architecture

arm64

Docker creation

created manually in portainer not with compose.

Container logs

no logs as it doesn't spin up enough to create any logs

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[github-actions]

A human has marked this issue as invalid, this likely happened because the issue template was not used in the creation of the issue.

[shandshellin]

How is it invalid if your image won't work for the advertised architecture? I see no other area to post the question. Please advise.

[Roxedus]

How can you say its failing, if you cant prove it with logs?

[j0nnymoe]

Provide us logs/errors that shows the image doesn't work.

[shandshellin]

no logs are created because it can't fire up the image to do so. Is there a specific tag i need to use to specify arm64 image? Seems like it is getting a non arm image.

[Roxedus]

no, there is not another tag you need to use.

[j0nnymoe]

You must be getting -some- error when creating as if the image didn't work for arm64, it would error out at creation.

[shandshellin]

can i specify an arm64 image for an older version? arm64v8-1.14.0 or something to force it?

[shandshellin]

will this image run in non-privilaged mode? That could be party of the hangup.

[j0nnymoe]

privilaged mode is required.

[Roxedus]

requires being run in privileged mode

Pulling a specific tag would not solve the root cause, which we are very interested in figuring out. What exactly happens when you run it?

[shandshellin]

it's a swarm, doesn't work with privilaged containers generally. I've had other images require the specific tag because it wasn't detecting arch correctly and trying to push an x86 or the image has no arm64 support even thought it is listed for that image.

[Roxedus]

Our tags are listed on dockerhub, as well as on the package info here on github

[shandshellin]

lol so were theirs. Pretty sure privilaged is the problem here, not the image. Thanks for the info.

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions]

This issue is locked due to inactivity