You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Konstantine Karantasis (Jira)" <ji...@apache.org> on 2020/04/06 03:57:00 UTC
[jira] [Resolved] (KAFKA-8417) Remove redundant network definition
--net=host when starting testing docker containers
[ https://issues.apache.org/jira/browse/KAFKA-8417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konstantine Karantasis resolved KAFKA-8417.
-------------------------------------------
Resolution: Fixed
> Remove redundant network definition --net=host when starting testing docker containers
> --------------------------------------------------------------------------------------
>
> Key: KAFKA-8417
> URL: https://issues.apache.org/jira/browse/KAFKA-8417
> Project: Kafka
> Issue Type: Bug
> Components: system tests
> Reporter: Konstantine Karantasis
> Assignee: Konstantine Karantasis
> Priority: Major
>
> The switches {{--net}} and {{--network}} are equivalent in docker, with the latter being preferred.
> (see [https://github.com/docker/cli/blob/master/cli/command/container/opts.go] where currently there's the comment: _// We allow for both "--net" and "--network", although the latter is the recommended way._)
> However, in recent Docker versions, defining both as follows:
> {{--net=host --network ducknet}}
> fails with error:
> {{docker: conflicting options: cannot attach both user-defined and non-user-defined network-modes.}}
> Removing {{--net=host}} and keeping only the user-defined network should fix the issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)