Replies: 8 comments
-
What do you see if you start it without |
Beta Was this translation helpful? Give feedback.
-
Nothing shows up at all. In Portainer, Status is |
Beta Was this translation helpful? Give feedback.
-
My guess was totally correct, doing I now pulled using the digest id, Why is this even happening? |
Beta Was this translation helpful? Give feedback.
-
What does You could also try upgrading to Docker 20.10.x since the 19.03.x branch is pretty much dead anyway. |
Beta Was this translation helpful? Give feedback.
-
I'm using latest release of LibreELEC 10 and Docker 19.03.x is the only version available. The one I'm using now is:
|
Beta Was this translation helpful? Give feedback.
-
Well, it's up to the local Docker install to select the proper image based on its local arch, so if it's not doing that, you should probably bring it up with the LibreELEC project. Maybe they ship a build of Docker with their own patches, or maybe the issue is fixed in a later version of Docker. I have access to an ARMv8 machine running Docker 20.10.x, and it pulls the correct image there. Using |
Beta Was this translation helpful? Give feedback.
-
You might be right as this could be a distro related or docker version issue. I'll see if I can ask the Team LibreELEC to update the Docker to the latest version.
|
Beta Was this translation helpful? Give feedback.
-
These were indeed also issues which other users reported having with docker and multi-arch images. Not sure if you can update the docker daemon on it? If it is Debian based then you could take a look here: https://docs.docker.com/engine/install/debian/ |
Beta Was this translation helpful? Give feedback.
-
Subject of the issue
Unable to get
vaultwarden/server:latest
image to work on ARM64v8.Deployment environment
vaultwarden version: N/A
Install method: Docker cli
Clients used: Android
Reverse proxy and version: Couldn't even get to this part.
MySQL/MariaDB or PostgreSQL version: N/A
Other relevant details: N/A
Steps to reproduce
docker pull vaultwarden/server:latest
Expected behaviour
The container should start normally.
Actual behaviour
The container doesn't start at all and goes into bootloop with nothing showing up in container logs.
Troubleshooting data
There is only root user from which evrything is installed through.
Beta Was this translation helpful? Give feedback.
All reactions