Question: I would like to redirect all URLs to https on my host and root folder to sub-folder.

My configuration:

```
Redirect permanent / https://myhost.com/ 
RedirectMatch ^/$ /sub-folder/

```

The first redirect works well, all http requests are redirected to https, but the second one does nothing. 

Any advice, please?

Thanks.

Answer: 
The solution was as simple as stated in the linked article. I am not sure why my configuration did not change the first time I restarted the docker daemon.

After I found evidence in the [Docker daemon documentation](https://docs.docker.com/engine/reference/commandline/dockerd/) for the bridge argument in daemon.json, I gave it another try and the docker daemon picked up the KVM default bridge on startup.

First I created the configuration file `/etc/docker/daemon.json` as suggested in the documentation with the following content (the iptables line may not even be needed):

```
{
"bridge": "virbr0",
"iptables": false
}

```

all that was needed was:

```
docker stop mysql
systemctl stop docker
systemctl start docker
docker start mysql

```

And the existing docker container was running on the KVM bridge. The IP address of the container can be checked with:

```
docker inspect -f '{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' mysql
192.168.122.2

```

I am not sure if I can remove the docker0 bridge now, but the container is listed under virbr0 together with the three VMs.

```
brctl show
bridge name bridge id           STP enabled interfaces
docker0     8000.024241f39b89   no      
virbr0      8000.068ff2a4a56e   yes         veth2abcff1
                                            virbr0-nic
                                            vnet0
                                            vnet1
                                            vnet2

```
When I read the question, I was looking to see if there was a way to connect `virbr0` to a Docker network. The image below is my modification of what I think was being asked:

[![enter image description here](https://i.stack.imgur.com/AYcvD.png)](https://i.stack.imgur.com/AYcvD.png)

If that is the case, the answer is to use a `macvlan` network, which allows you to attach a docker network directly to a host device. So something like the following would get you what you want:

`docker network create --driver=macvlan --subnet=192.168.0.0/16 -o parent=virbr0 mynet`