Skip to content

[Request]: Add option to create/run a container that has no network attachment. #386

@jglogan

Description

@jglogan

Feature or enhancement request details

The current default for create and run recognizes that the most common use case is to attach a container to the default network.

We could define a special network name none but possibly better would be to have a --no-network flag. In either case the client should validate the network options for a container and reject inconsistent inputs.

Code of Conduct

  • I agree to follow this project's Code of Conduct

Metadata

Metadata

Assignees

No one assigned

    Labels

    good first issueGood for newcomersnetworkIssues and features associated with networking and DNS.nextItems in scope for the next few milestones

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions