Docker Template

This site is best viewed in a modern browser with JavaScript enabled.

Docker Template

Tommiy

Hi, I just updated eve-ng community version to reinclude docker use fixing up the items that didn't work in the wrapper and in various other places. For the template I needed to add in a docker options field pretty much like qemu options as most of the container apps such as cSRX etc have environmental variables that need to be passed into the container.

Outside of that I'd love to see sonic in a container running. Spare time for that is my constraint.

Looking forward to seeing the beta sounds interesting.

Lauster

I'd love to get patches and/or an explanation of how you did it.

breakintheweb

Lauster

If you have interest in discussing this topic, please do it offline. There is already a lot of confusion between Qewig and EVE-NG and I'd like to avoid it as much as possible in the future. Hopefully you'll like Qewig enough when it's realeased, it won't be a huge concern for you

breakintheweb

We've been building the docker support in to Qewig to allow users to add their own custom docker images. Currently we have the ability to map exposed ports to the containers. You can define what ports and services you want to mapped to a container and it will pass it though to the docker. We also have custom options which can be passed in addition to just the ports.

Lauster

Nice! - that makes doing things like TACACS+ and dns and so much much easier.

Tommiy

The QEwig solutin seems to be heading down a smilar path that all services are exposed across the bridge. How is this going to handle a 24 port OvS switch for example? I don;t need or want external access to the ethernet ports but I do want those ports to interact with the rest of the network switches in the lab. Consider OvS, Openswitch etc or even te Juniper cSRX. How is QEWig set up to handle these types of images?

breakintheweb

Tommiy

I didn't fully understand your question, but I Can explain how it works it Qewig. In Qewig, everything is an ovs. If you have a link between two nodes, an ovs, will be created and the links for the nodes will be attached. To connect more than two nodes to the same network, you create a "network" (which is just an OVS) and then attach the interfaces you want. For external connectivity, you would add a "network" and then add one of the physical interfaces from the handler in to that network (ovs).

Not sure if that answers your question, but if not, you can provide a more detailed example and I'll try to explain more.

Tommiy

I'm not sure that it does but perhaps I'm getting confused between your response about Docker and management through its bridge.

Let say I have a containerised OpenSwitch which has 24 virtual ports into the container. The first port (or another port) would be for management and the remaining normal data ports. Does QEWig support having the management through the bridge and the data ports being capable of connecting to the OVS port described in the last response? By the sounds of it you are just using OVS to create a bridge to join ports together and potentially giving the bridge an IP for an external or layer 3 interface.

breakintheweb

Tommiy

If you create a container with 24 ports, all 24 ports will be available in Qewig to connect to what you want. The only difference with docker is that an additional interface will be created for the docker node to allow for connectivity to any exposed ports.

For example you could containerize an OpenSwitch with 24 ports and a web gui for mgmt on port 80 (or multiple ports). You could then connect to the OpenSwitch outside of the lab for mgmt.

Tommiy

And can i pass environmental variables into the docker container from the template? Juniper cSRX for instance requires passing in the admin user/password such that you can then subsequentially manage it. Re Juniper reference page.

https://www.juniper.net/documentation/en_US/csrx/topics/reference/general/security-csrx-environment-variables.html