You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Creating container doesn't allow for setting "NetworkingConfig" #2555
In order to attach a container to more than one network on creation the "NetworkingConfig" field is needed but the com.github.dockerjava.api.command.CreateContainerCmd does not publish the value (for potential manipulation)
The problem is that in com.github.dockerjava.core.command.CreateContainerCmdImpl#exec the value is overwritten so just providing a getter is not quite enought and the exec needs to be adapted as well
I’m also blocked by this issue. From my understanding, it’s currently not possible to set the MAC address of a container because the CreateContainerCmd implementation doesn’t expose a way to configure it at creation time.
As a result, we’re currently forced to use a workaround via reflection to set it manually, which is fragile and not ideal. The proposed PR seems like it would solve this problem, as allowing NetworkingConfig to be set during container creation would enable specifying the MAC address along with other network settings.
Activity
SchwoebelDa commentedon Jan 23, 2026
I’m also blocked by this issue. From my understanding, it’s currently not possible to set the MAC address of a container because the CreateContainerCmd implementation doesn’t expose a way to configure it at creation time.
As a result, we’re currently forced to use a workaround via reflection to set it manually, which is fragile and not ideal. The proposed PR seems like it would solve this problem, as allowing NetworkingConfig to be set during container creation would enable specifying the MAC address along with other network settings.