unable to create macvlan from gui or cli

  • Hi!


    I'm new to omv, docker, and all that. I'm trying to get pihole set up, and I'm stuck near the beginning.


    I'm basically following these guides:

    Install Pi-Hole on OMV with DOCKER COMPANY AND DEDICATE IP » TheJoe.it
    Install Pi-Hole on OMV with DOCKER COMPANY AND DEDICATE IP » Networking
    thejoe.it


    I understand that first I need to create a new docker macvlan network, for which i am following https://wiki.omv-extras.org/do…te_a_vlan_pi-hole_adguard. That fails, though, either through the gui or directly though the cli.


    Here's the cli command:

    Code
    > docker network create --driver macvlan --opt parent=enp1s0 --opt macvlan_mode=bridge --subnet= 192.168.50.0/24 --gateway=192.168.50.1 --ip-range= 192.168.50.240/29  --aux-address="my-router=192.168.50.1" --aux-address="my-nas=192.168.50.54" piholevlan 2>&1

    I get the same error in either via gui or cli:


    Code
    500 - Internal Server Error
    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LC_ALL=C.UTF-8; export LANGUAGE=; docker network create --driver macvlan --opt parent=enp1s0 --opt macvlan_mode=bridge --subnet= 192.168.50.0/24 --gateway=192.168.50.1 --ip-range= 192.168.50.240/29 pihole-vlan 2>&1' with exit code '1': docker: 'docker network create' requires 1 argument Usage: docker network create [OPTIONS] NETWORK Run 'docker network create --help' for more information

    Any idea where this is going wrong?

  • votdev

    Approved the thread.
  • This command is failing:


    docker network create --driver macvlan --opt parent=enp1s0 --opt macvlan_mode=bridge --subnet= 192.168.50.0/24 --gateway=192.168.50.1 --ip-range= 192.168.50.240/29 pihole-vlan


    This is the error message returned from docker:


    'docker network create' requires 1 argument

    Usage: docker network create [OPTIONS] NETWORK

    Run 'docker network create --help' for more information


    I notice that you have spaces between the --subnet= and --ip-range= options and the IP addresses that follow them. That would be the first thing to fix.

  • you have spaces between the --subnet= and --ip-range= options and the IP addresses that follow them. That would be the first thing to fix.

    And, that fixed it, thanks! (I won't embarrass myself further by saying how long I spent trying to figure out what was wrong before registering and posting a question)

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!