Network Bridge Docker fail to start

[nvarney]

Hi all,

I'm trying to create a simple CentOS 7 container on my TS-251 with Network Bridging configuration with DHCP. I get the following error:

Code: Select all

Failed to start container

Error Code: 500
Message: 500 Server Error: Internal Server Error ("IpamDriver.RequestAddress: No JSON object could be decoded")

If I use a Bridge with static IP configuration, the container start without any problem.
If I use a NAT configuration, the container start without any problem.

I don't know if what's going wrong with DHCP.

Is any of you have an idea ?

Regards,

Nicolas

[lab221]

Hi,

It all works fine in my NAS.
Do you use the latest version of Container Station v1.6.1701 and Firmware 4.2.2 2016/09/01 ?
Because 500 Server Error means something has gone wrong from internal.
I hope your problem will be solved after using the latest version

[Messiah62]

I have this same problem. I am not using 2016/09/01

[oni303]

I have same problem, too

ts-451+ Firmware: 4.2.2
Container Station: Version 1.6.1709

[DasUrmel]

I have the same Problem

Modell:TS-563
Firmwareversion:4.2.2
Date:2016-12-14

[parkerc]

Hi

I have something similar to this too..

Code: Select all

Failed to start container

Error Code: 500
Message: 500 Server Error: Internal Server Error ("IpamDriver.RequestAddress: Qnet IPAM IPv4 address already in use")

Was a fix (and root cause) ever found for this ?

[BryceWilkins]

Hello...I have a similar issue...related to creating a pi-hole container. In my case the error is:

Code: Select all

Background task error for create pihole: 500 Server Error: Internal Server Error ("IpamDriver.RequestAddress: Qnet IPAM cannot discover any DHCP server")

Anyone come across this error?

[parkerc]

The ipamDriver errors I was getting look like they related to the qnap virtual switch - not exactly sure how, but I wanted to come back to this post to say that I installed Portainer.io (qnapclub qpkg) to,see what that was like and it turns out once you have created a TLS connection to your QNAP Docker/Container setup, there is an option Portainer gives you within each Container to change the network options - something missing with Container Station.

Being able to change the network setting via Portainer fixed my issue

viewtopic.php?f=320&t=133975