testcontainers-java: Can not set custom container name

Tried to set container name via .setContainerName(), however upon start container still has some random name assigned to it automatically. Did anyone test this? Works from command line with docker run -d --name bla my/image

About this issue

Original URL
State: closed
Created 8 years ago
Comments: 16 (9 by maintainers)

Most upvoted comments

Dont mind. I found a nice workaround:

            .withCreateContainerCmdModifier(new Consumer<CreateContainerCmd>() {
                @Override
                public void accept(CreateContainerCmd createContainerCmd) {
                    createContainerCmd.withHostName(CNAME);
                    createContainerCmd.withName(CNAME);
                }
            })

HaVonTe1 on Jan 16, 2018

The documentation of withCreateContainerCmdModifier says:

Warning: this does expose the underlying docker-java API so might change outside of our control.

To me, this seems like a strong indication for extending the interface of GenericContainer.

claussni on Jan 28, 2020

IMHO there is always a way to screw things up when configuring containers and hiding existing docker functionality isn’t gonna make testcontainers more valuable. Also it would make sense adding container labelling.

pavelpp on Jan 18, 2017

I’m initializing cluster of 3 etcd nodes, where I should link them during start command and this .withNetworkAliases("foo") works perfectly for me, thanks!

IgorPerikov on Feb 23, 2018

@RobMaskell if you use Networks you can (and should) use withNetworkAliases to provide a DNS name for your container, see: https://github.com/testcontainers/testcontainers-java/blob/4471878f332dd8e7880fc8a55879a45834556e5e/core/src/test/java/org/testcontainers/containers/NetworkTest.java#L23

bsideup on Feb 11, 2018