<div>
802.11q does not exist....it is 802.11 &nbsp;(which is WiFi) a carrier for signalsof 802.1 (a method for data transfer using a variety of carriers), 802.3 for ethernet, 802.4 for token bus, 802.5 for tokern ring, 802.11 for wireless). 802.1q is a standard for 802.1 to multiplex multiple "networks" across one cable. (and thus allow multiple virtual lans to exist in a network).802.1q adds 4 bytes to each packet, 2 bytes indicate that it is a 802.1q tag and 2 bytes carrying the priority &amp; vlan "tag" MACvlan is something else completely It's more like a bridge done differently, and besides the host doing the separation the network is one mixed pool of packet no separation. The following article may help a bit:https://sreeninet.wordpress.com/2016/05/29/macvlan-and-ipvlan/ 
</div>

<div>
Thanks for correcting me on my misunderstanding. Having read the article you shared I believe what I would like to try to use is MACvlan <pre><code class="code-1 nolinks" id="code-20-43028199-1">root@ubuntu_server:/home/beatified# docker network ls
NETWORK ID &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;NAME &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;DRIVER &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;SCOPE
07ebf1438c44 &nbsp; &nbsp; &nbsp; &nbsp;bridge &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;bridge &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;local
531f76dbf73a &nbsp; &nbsp; &nbsp; &nbsp;hassio &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;bridge &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;local
84518888339f &nbsp; &nbsp; &nbsp; &nbsp;home-macvlan &nbsp; &nbsp; &nbsp; &nbsp;macvlan &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; local
ea325f18008d &nbsp; &nbsp; &nbsp; &nbsp;host &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;host &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;local
fe61df62865e &nbsp; &nbsp; &nbsp; &nbsp;none &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;null &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;local
</code></pre><pre><code class="code-10 nolinks" id="code-20-43028199-2">root@ubuntu_server:/home/beatified# docker network inspect home-macvlan
[
&nbsp; &nbsp; {
&nbsp; &nbsp; &nbsp; &nbsp; "Name": "home-macvlan",
&nbsp; &nbsp; &nbsp; &nbsp; "Id": "84518888339f9f25ceca2120ae6611b0407687190640d55dddd18656fa12854c",
&nbsp; &nbsp; &nbsp; &nbsp; "Created": "2020-02-06T21:37:54.348743211Z",
&nbsp; &nbsp; &nbsp; &nbsp; "Scope": "local",
&nbsp; &nbsp; &nbsp; &nbsp; "Driver": "macvlan",
&nbsp; &nbsp; &nbsp; &nbsp; "EnableIPv6": false,
&nbsp; &nbsp; &nbsp; &nbsp; "IPAM": {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "Driver": "default",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "Options": {},
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "Config": [
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "Subnet": "192.168.20.0/24",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "Gateway": "192.168.20.1"
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; }
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ]
&nbsp; &nbsp; &nbsp; &nbsp; },
&nbsp; &nbsp; &nbsp; &nbsp; "Internal": false,
&nbsp; &nbsp; &nbsp; &nbsp; "Attachable": false,
&nbsp; &nbsp; &nbsp; &nbsp; "Ingress": false,
&nbsp; &nbsp; &nbsp; &nbsp; "ConfigFrom": {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "Network": ""
&nbsp; &nbsp; &nbsp; &nbsp; },
&nbsp; &nbsp; &nbsp; &nbsp; "ConfigOnly": false,
&nbsp; &nbsp; &nbsp; &nbsp; "Containers": {},
&nbsp; &nbsp; &nbsp; &nbsp; "Options": {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "parent": "ens160.20"
&nbsp; &nbsp; &nbsp; &nbsp; },
&nbsp; &nbsp; &nbsp; &nbsp; "Labels": {}
&nbsp; &nbsp; }
]


</code></pre>This is what I've got at this point. I dont know if its correct at all but your advise would be very welcomed. For the time being attaching a simple nginx instance to this network would teach me what I need to know. If you can help me further I would be very grateful. Thanks
</div>

<div>
You seem to have a 802.1q vlan with tag 20 (derived from the name of the interface: &nbsp;<span style="color: rgb(0, 0, 0); font-family: Courier, monospace; font-size: 12px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: left; text-indent: 0px; text-transform: none; white-space: pre; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(249, 251, 253); text-decoration-style: initial; text-decoration-color: initial; display: inline !important; float: none;">ens160.20 ) Did you configure VLAN 20 anywhere else on the link to ens190?If not then better drop the .20...
</div>

<div>
No I didn't but the idea was to connect it to vlan 20. Is this possible?
</div>

<div>
ok VLAN 20 can be used, &nbsp;you need vlan 20 on all the equipment connected to this device.And this vlan 20 needs to be the the 192168.20.0/24 address range and the default gateway in the network needs to be: 192.168.20.1 ( and is not your docker host, but the router that connects to the other networks.). 
</div>

<div>
So I have VLAN 20 configured on the network but ens190 is not configured to use that vlan specifically. It is available on the wire but the nic is not connected via that vlan. Does this nic need to be configured on vlan 20 first? If so I will just buy some pcie nics and add some capability to my server.
</div>

<div>
The fact you specified ens190.20 (the .20) makes docker create the needed VLAN on the interface.You can interact with ens190.20 if your switch produces a taged vlan20 on the other end of the cable.Most modern adapter can handle VLANs (which are &gt;1500 byte packets. ) 
</div>

<div>
So as of right now its not working and I wonder if it has to do with the fact that Docker is running on Ubuntu Server as a VM on ESXi 6.7. Could that be an issue?
</div>

beatified

<div>
I think I had to specifiy a driver this was likely my issue all along. On top of the fact that I needed to learn more about how to spin up containers and the possible switches and arguments. The issue seems to be resolved. Thanks for your help.
</div>

<div>
<div class="content wysiwyg-content">
This one is really getting to me. I would like to run most of my docker containers by connecting them to a vlan on my Ubiquiti network but cant seem to get it working. although admittedly I don't know much about docker and I'm still very new to it. 
 
I have tried creating a macvlan for one of the networks and that seems to be alright but I cant seem to get my containers connected to it. 
 
I would like to connect to my vlan at 192.168.20.0/24 just doing that with an nginx container or something would be a great example for me to go by. 
 
Thanks in advance for your help. 
 
Stuart
</div>
</div>

This one is really getting to me. I would like to run most of my docker containers by connecting them to a vlan on my Ubiquiti network but cant seem to get it working. although admittedly I don't know much about docker and I'm still very new to it.

I have tried creating a macvlan for one of the networks and that seems to be alright but I cant seem to get my containers connected to it.

I would like to connect to my vlan at 192.168.20.0/24 just doing that with an nginx container or something would be a great example for me to go by.

Thanks in advance for your help.

Stuart

Docker container conneced to 802.11Q Network

Docker is a computer program used to run software packages called containers in an operating-system-level virtualization process called containerization. It’s developed by Docker, Inc. and was first released in 2013.

Docker

Networking is the process of connecting computing devices, peripherals and terminals together through a system that uses wiring, cabling or radio waves that enable their users to communicate, share information and interact over distances. Often associated are issues regarding operating systems, hardware and equipment, cloud and virtual networking, protocols, architecture, storage and management.

Networking

Golang, also called Go, is an open source programming language that is a statically-typed language with syntax loosely derived from C, adding automatic memory management, type safety, some dynamic-typing capabilities, additional built-in types such as variable-length arrays and key-value maps, and a large standard library. Go is a general-purpose systems programming language that aims to be efficient both for development and execution with a focus on fast compilation and increased maintainability of large projects. Go was originally targeted at systems programming tasks such as building server/web applications, high throughput middleware and databases.