Docker container failed to run.

Skip to first unread message

Shaji Markose

Feb 1, 2024, 5:06:32 PMFeb 1
to xnat_discussion
I recently changed docker swarm to a new VM. Loaded images in the new server and joined the as worker node (docker swarmp join). Everything went well and the container run as expected. However, couple of days later the docker images failing to run. . Also noticed that the Images & Commands (Administer->Plugin Settings->Images & Commands) section got wiped out. The error is attached.
 Appreciate any help.


Shaji Markose

Feb 2, 2024, 12:24:07 AMFeb 2
to xnat_discussion
The conatiner.log gives the following:
2024-02-01 22:39:03,280 [ajp-nio-0:0:0:0:0:0:0:1-8009-exec-25] ERROR org.nrg.containers.api.DockerControlApi - Failed to list images. Request error: GET unix://localhost:80/images/json: 200
org.mandas.docker.client.exceptions.DockerRequestException: Request error: GET unix://localhost:80/images/json: 200
        at org.mandas.docker.client.DefaultDockerClient.propagate(
        at org.mandas.docker.client.DefaultDockerClient.request(
        at org.mandas.docker.client.DefaultDockerClient.listImages(
        at org.nrg.containers.api.DockerControlApi._getImages(
        at org.nrg.containers.api.DockerControlApi.getImages(
        at org.nrg.containers.api.DockerControlApi.getAllImages(
        at org.springframework.cglib.proxy.MethodProxy.invoke(
        at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
        at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(
        at sun.reflect.GeneratedMethodAccessor427.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(
        at java.lang.reflect.Method.invoke(
        at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(

There is more. I can attach if needed.


Evi Vanoost

Feb 2, 2024, 1:17:02 PMFeb 2
to xnat_discussion
This seems to be an issue when your Docker version goes to v25. We just ran into that today. Downgrade to Docker 24.0.9 for now.
(on RHEL) - yum downgrade docker-ce-3:24.0.9-1.el9.x86_64
I've got similar errors in the logs, seems to be an issue with the container service API needing to be updated?

Evi Vanoost

Feb 2, 2024, 1:19:35 PMFeb 2
to xnat_discussion
Caused by: com.fasterxml.jackson.databind.exc.ValueInstantiationException: Cannot construct instance of `org.mandas.docker.client.messages.ImmutableImage$Builder`, problem: Cannot build Image, some of required attributes are not set [virtualSize]
 at [Source: (org.glassfish.jersey.message.internal.ReaderInterceptorExecutor$UnCloseableInputStream); line: 1, column: 3138] (through reference chain: java.util.ArrayList[0])
        at org.glassfish.jersey.client.JerseyInvocation.translate(
        at org.glassfish.jersey.client.JerseyInvocation.lambda$invoke$2(

  • The VirtualSize field in the GET /images/{name}/jsonGET /images/json, and GET /system/df responses is now omitted. Use the Size field instead, which contains the same information.

Shaji Markose

Feb 2, 2024, 3:06:33 PMFeb 2
I am using version 1.44. We haven't updated the version recently. 

You received this message because you are subscribed to the Google Groups "xnat_discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To view this discussion on the web visit

Richard Cole

Feb 2, 2024, 4:49:08 PMFeb 2
Have you mounted the "/data/xnat" to your new worker?  Confirm your NFS mounts..

Evi Vanoost

Feb 20, 2024, 2:29:50 PMFeb 20
to xnat_discussion
Any updates on this bug?
It seems to me the Docker container service needs to be updated, unsure where the code lives to do this.

John Flavin

Feb 20, 2024, 4:49:09 PMFeb 20

Sorry about the lack of response.


Yes, solving this will require an update to the Container Service. However, it isn’t exactly a straightforward fix. The issue is occurring in an upstream dependency, and there are difficulties which prevent us from upgrading that dependency.


For the time being, if possible, please avoid upgrading docker while we work on a fix. Sorry that I don’t have a better answer at the moment.


John Flavin


From: <> on behalf of Evi Vanoost <>
Date: Tuesday, February 20, 2024 at 1:30
To: xnat_discussion <>
Subject: External: Re: [XNAT Discussion] Re: Docker container failed to run.

You don't often get email from Learn why this is important


Apr 17, 2024, 1:42:24 PMApr 17
to xnat_discussion
Hi all, is the solution to this still to downgrade to docker v24? I believe xnat 1.8.10 and container-service 3.4.3 were both released since the last post in this thread.

I recently updated system packages and xnat build, and am running into the same problem with my xnat-docker-compose instance.

Ford McDonald

Apr 17, 2024, 2:35:54 PMApr 17
to xnat_discussion
This solution worked for me, as of yesterday.  Just downgrade and restart your docker service.

Here is the working list of installed packages and their versions:                  1.6.9-3.1.el8                            @docker-ce-stable

docker-buildx-plugin.x86_64           0.13.1-1.el8                             @docker-ce-stable

docker-ce.x86_64                      3:24.0.9-1.el8                           @docker-ce-stable

docker-ce-cli.x86_64                  1:24.0.9-1.el8                           @docker-ce-stable

docker-ce-rootless-extras.x86_64      26.0.1-1.el8                             @docker-ce-stable

docker-compose-plugin.x86_64          2.26.1-1.el8                             @docker-ce-stable

Reply all
Reply to author
0 new messages