# Custom ISO for disabling system-docker bridge

**URL:** <https://forums.suse.com/t/custom-iso-for-disabling-system-docker-bridge/13308>\
**Category:** RancherOS\
**Created:** [February 12, 2019, 9:41pm UTC](https://forums.suse.com/t/custom-iso-for-disabling-system-docker-bridge/13308 "2019-02-12T21:41:53Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ehlomarcus](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/ehlomarcus/32/4839_2.png) [@ehlomarcus](https://forums.suse.com/u/ehlomarcus)\
**Post date:** [February 12, 2019, 9:41pm UTC](https://forums.suse.com/t/custom-iso-for-disabling-system-docker-bridge/13308/1 "2019-02-12T21:41:53Z")

</div>

Hi

This question is very much related to [Setting the docker-sys Network](http://forums.suse.com/t/setting-the-docker-sys-network/6973) since we are affected by the usage of 172.18.0.0/16 as bridge network on system-docker.

We resolved it at first by using cloud-config.yaml, but that became a problem when we booted a machine on a 172.18 network. Then there is a momen-22 where cloud-config.yaml need to be downloaded from an url which resolves to a 172.18 ip.

This lead us to building our own custom iso, to disable the system-docker bridge by setting “bridge: none” in os-config.tpl.yml.

Creating a image for 1.4.2 and 1.5.0 where ok, but has now failed with the 1.5.1 release.

So what is the preferred way of creating a custom iso for vmware?

I got to the point where kvm is needed?! why?!