Docker image not accessible in Azure ACI

[lemonsmatt]

Tried to start my server today on ACI and got the following error:

containerinstance.ContainerGroupsClient#CreateOrUpdate: Failure sending request: StatusCode=400 -- Original Error: Code="InaccessibleImage" Message="The image 'lloesche/valheim-server' in container group 'valheim-server' is not accessible. Please check the image and registry credential."

Was able to point it to the debian tag and start it up with that however.

[epoksii]

same here, no changes done in ACI configuration, yesterday automation failed to start the the container instance. Error: The image 'lloesche/valheim-server' in container group 'valheimserver' is not accessible. Please check the image and registry credential.

Can also confirm that deploy with debian10 tag works.

[MrAdam]

I'm running Unraid, and it's giving me a "not available" error when checking for new versions - I'm assuming it's related

[UniDev95]

Tried to start my server today on ACI and got the following error:

containerinstance.ContainerGroupsClient#CreateOrUpdate: Failure sending request: StatusCode=400 -- Original Error: Code="InaccessibleImage" Message="The image 'lloesche/valheim-server' in container group 'valheim-server' is not accessible. Please check the image and registry credential."

Was able to point it to the debian tag and start it up with that however.

I seem to have also run into this startup error for my container instance this morning. Could you point me to how you updated to the debian tag?

[akoumoundouros]

@UniDev95 I also started seeing this error and switched to the debian image lloesche/valheim-server:debian10

[The-DevBlog]

has anyone found a fix for this? @akoumoundouros I tried using lloesche/valheim-server:debian10. I was able to successfully create my server, but whenever I tried to connect, I would get a 'failed to connect' error.

[akoumoundouros]

@AndrewCS149 I believe that server version doesn't support crossplay, are you trying to connect from console or pc?

[epoksii]

has anyone found a fix for this? @akoumoundouros I tried using lloesche/valheim-server:debian10. I was able to successfully create my server, but whenever I tried to connect, I would get a 'failed to connect' error.

If you have crossplay enabled on variables the docker version doesn't start it seems. I actually resorted to creating a private azure container repository where i copied this one and now build the container from there until this gets fixed.

[The-DevBlog]

@akoumoundouros I was trying to connect from PC, but I did have the -crossplay env variable enabled. So that was probably it. Strange though, because looking at the logs, it looked like everything booted up fine. I even saw the 'Dungeondb start' message.

Anyways, what I ended up doing is spinning up a linux VM and then followed the 'docker-compose' instructions on the lloesche/valheim-server github: https://github.com/lloesche/valheim-server-docker#deploying-with-docker-compose

[MrAdam]

Using the fully qualified image path ghcr.io/lloesche/valheim-server instead of just lloesche/valheim-server fixed it for me.

[The-DevBlog]

Good to know. Thanks @MrAdam !

[lloesche]

Looks like a temporary issue with Dockerhub. I tested right now and it was working fine for me:

We're uploading the Docker image to two redundant registries for situations like this. Dockerhub: lloesche/valheim-server Github Container Registry: ghcr.io/lloesche/valheim-server

Let me know if this is still an issue for anyone.

[nickelia21]

Has this issue been fixed yet? Still can start the server, but unable to connect in-game with the debian10 tag. Using ghcr.io/lloesche/valheim-server does not even let me start the server.

Could this be due to the new cross-platform feature? I'm trying to connect via Xbox.

[lhuswe]

I had the same issue when i tried to deploy a server in azure, used this as a workaround -> image: lloesche/valheim-server@sha256:10b4b84b68b0be077b8ec878a8b786df7ab45a29f356c7b9c151482167214f0e

[nickelia21]

I had the same issue when i tried to deploy a server in azure, used this as a workaround -> image: lloesche/valheim-server@sha256:10b4b84b68b0be077b8ec878a8b786df7ab45a29f356c7b9c151482167214f0e

Using this as the image, the server is now able to be created and hosted by Azure successfully, but unable to connect on Xbox. Do I need to add a YAML tag for this, or is there some other workaround?

[lhuswe]

I had the same issue when i tried to deploy a server in azure, used this as a workaround -> image: lloesche/valheim-server@sha256:10b4b84b68b0be077b8ec878a8b786df7ab45a29f356c7b9c151482167214f0e

Using this as the image, the server is now able to be created and hosted by Azure successfully, but unable to connect on Xbox. Do I need to add a YAML tag for this, or is there some other workaround?

Did you enable crossplay? I had to add this in the yml-file ->

      - name: SERVER_ARGS
        value: -crossplay

[nickelia21]

valheim_server.txt

Here's my YML file but in TXT format.

To create the server instance in Azure, I'm running this command: az container create -g valheimserver-eastus -f valheim_server.yml

[ndamulelonemakh]

I just had this issue; in my case, everything was okay except the Registry Login Server. If your docker image resides in a Private Repository, you must use index.docker.io instead of docker.io, which applies to public images. I feel like blaming someone but I dont know who to blame between me, azure and docker 🤔