Posts by skullkidrae

skullkidrae · 2026-01-12T01:58:49+01:00

Quote from chente

I'm sorry, I'm out of ideas.

ok. i think iv got it running. i ended up copying and repasting the repo i was using so i may of deleated something i shouldnt have prevously. it seems to run in docker but i cant access the pihole gui using the assigned ip address.

skullkidrae · Sunday, 10:02 pm

Quote from chente

I'm sorry, I'm out of ideas.

out of cuiosity. why is it showing as end0 not eth0?

skullkidrae · Sunday, 8:59 pm

Quote from chente

I'm sorry, I'm out of ideas.

thanks for trying.

skullkidrae · Sunday, 6:05 pm

Quote from chente

does it work now?

unfortunitly not

Code

time="2026-01-11T17:04:38Z" level=warning msg="No services to build"
 Container pihole Starting 
Error response from daemon: failed to set up container networking: network 3b4e2c8063f902397af28f4a95d773d0a0f6e4f4fe010921751566589b3e76df not found


*** ERROR #1 ***


END OF LINE
█

skullkidrae · Sunday, 5:43 pm

Quote from chente

ryecoaaron
Can you take a look at this? Shouldn't the network interface end0 appear in the "parent" field instead of being empty?

i may of missed the parent network in a prevous attempt. i had correct this in my most recent attempt and its showing when inspecting the network now though.

Code

[
  {
    "Name": "mynet",
    "Id": "26d2075d9f186f5dfe59062c4f4c27625ffc4ac183b5b2c3c2488b747113b129",
    "Created": "2026-01-11T16:08:41.814337541Z",
    "Scope": "local",
    "Driver": "macvlan",
    "EnableIPv4": true,
    "EnableIPv6": false,
    "IPAM": {
      "Driver": "default",
      "Options": {},
      "Config": [
        {
          "Subnet": "192.168.4.0/24",
          "IPRange": "192.168.4.240/29",
          "Gateway": "192.168.4.1"
        }
      ]
    },
    "Internal": false,
    "Attachable": false,
    "Ingress": false,
    "ConfigFrom": {
      "Network": ""
    },
    "ConfigOnly": false,
    "Options": {
      "parent": "end0"
    },
    "Labels": {},
    "Containers": {},
    "Status": {
      "IPAM": {
        "Subnets": {
          "192.168.4.0/24": {
            "IPsInUse": 3,
            "DynamicIPsAvailable": 8
          }
        }
      }
    }
  }
]

END OF LINE

Display More

skullkidrae · Sunday, 5:09 pm

is there a way to check if im setting up my ip settings corectly?

skullkidrae · Sunday, 4:11 pm

restarted. same error.

Code

time="2026-01-11T15:17:11Z" level=warning msg="No services to build"
 Container pihole Starting 
Error response from daemon: failed to set up container networking: network 3b4e2c8063f902397af28f4a95d773d0a0f6e4f4fe010921751566589b3e76df not found


*** ERROR #1 ***


END OF LINE
█

skullkidrae · Sunday, 3:18 pm

Quote from chente

If you want to create a new interface, first delete the existing one. You should not create two network interfaces with the same network range.

thats what i did. deleated the docker interface and recreated it as mynet

skullkidrae · Sunday, 3:06 pm

Code

amended network


[
  {
    "Name": "mynet",
    "Id": "905962b73d27bcb0d8ff3d3fab0f081462e2e6cf7091d02d53dbc5b852bbdac9",
    "Created": "2026-01-11T14:02:42.187880835Z",
    "Scope": "local",
    "Driver": "macvlan",
    "EnableIPv4": true,
    "EnableIPv6": false,
    "IPAM": {
      "Driver": "default",
      "Options": {},
      "Config": [
        {
          "Subnet": "192.168.4.0/24",
          "IPRange": "192.168.4.240/29",
          "Gateway": "192.168.4.1"
        }
      ]
    },
    "Internal": false,
    "Attachable": false,
    "Ingress": false,
    "ConfigFrom": {
      "Network": ""
    },
    "ConfigOnly": false,
    "Options": {
      "parent": ""
    },
    "Labels": {},
    "Containers": {},
    "Status": {
      "IPAM": {
        "Subnets": {
          "192.168.4.0/24": {
            "IPsInUse": 3,
            "DynamicIPsAvailable": 8
          }
        }
      }
    }
  }
]

END OF LINE

Display More

skullkidrae · Sunday, 3:05 pm

Quote from chente

You called it "docker", not "mynet". Change the compose file to use the "docker" network.

ahh. ok. i tryed changing the network to dsocker but it didnt work so did the inverse and redid the network info to mynet. getting the following error

Code

time="2026-01-11T14:04:58Z" level=warning msg="No services to build"
 Container pihole Starting 
Error response from daemon: failed to set up container networking: network 3b4e2c8063f902397af28f4a95d773d0a0f6e4f4fe010921751566589b3e76df not found


*** ERROR #1 ***


END OF LINE
█

skullkidrae · Sunday, 2:30 pm

Quote from chente

The compose file looks correct. Except you can skip all the port mappings. This is because you're using a VLAN, so all the ports are exposed on that IP address.

So the only thing that might be missing is what raulfg3 already pointed out. Did you follow the steps here to create mynet? --> https://wiki.omv-extras.org/do…erface_with_ip_in_our_lan

ahh ok. yes i did. whither its correct or not is undetermined. my access points ip for some reason is 192.168.4.0 and my pi is ~.~.~.60

Code

[
  {
    "Name": "docker",
    "Id": "5bdcf22d4ac9638aaba51ae1d5d5b57cc143869c4d6b90eeff542d99a1af80e8",
    "Created": "2026-01-10T21:47:02.404170306Z",
    "Scope": "local",
    "Driver": "macvlan",
    "EnableIPv4": true,
    "EnableIPv6": false,
    "IPAM": {
      "Driver": "default",
      "Options": {},
      "Config": [
        {
          "Subnet": "192.168.4.0/24",
          "IPRange": "192.168.4.240/29",
          "Gateway": "192.168.4.1"
        }
      ]
    },
    "Internal": false,
    "Attachable": false,
    "Ingress": false,
    "ConfigFrom": {
      "Network": ""
    },
    "ConfigOnly": false,
    "Options": {
      "parent": "end0"
    },
    "Labels": {},
    "Containers": {},
    "Status": {
      "IPAM": {
        "Subnets": {
          "192.168.4.0/24": {
            "IPsInUse": 3,
            "DynamicIPsAvailable": 8
          }
        }
      }
    }
  }
]

END OF LINE
█

Display More

skullkidrae · Sunday, 12:51 pm

Quote from chente

Publish your compose file.

Code

services:
  pihole:
    container_name: pihole
    image: pihole/pihole:latest
    ports:
      # DNS Ports
      - "53:53/tcp"
      - "53:53/udp"
      # Default HTTP Port
      - "80:80/tcp"
      # Default HTTPs Port. FTL will generate a self-signed certificate
      - "443:443/tcp"
      # Uncomment the below if using Pi-hole as your DHCP Server
      #- "67:67/udp"
      # Uncomment the line below if you are using Pi-hole as your NTP server
      #- "123:123/udp"
    environment:
      # Set the appropriate timezone for your location from
      # https://en.wikipedia.org/wiki/List_of_tz_database_time_zones, e.g:
      TZ: 'Europe/London'
      # Set a password to access the web interface. Not setting one will result in a random password being assigned
      FTLCONF_webserver_api_password: 'correct horse battery staple'
      # If using Docker's default `bridge` network setting the dns listening mode should be set to 'ALL'
      FTLCONF_dns_listeningMode: 'ALL'
    # Volumes store your data between container upgrades
    volumes:
      # For persisting Pi-hole's databases and common configuration file
      - './etc-pihole:/etc/pihole'
      # Uncomment the below if you have custom dnsmasq config files that you want to persist. Not needed for most starting fresh with Pi-hole v6. If you're upgrading from v5 you and have used this directory before, you should keep it enabled for the first v6 container start to allow for a complete migration. It can be removed afterwards. Needs environment variable FTLCONF_misc_etc_dnsmasq_d: 'true'
      #- './etc-dnsmasq.d:/etc/dnsmasq.d'
    cap_add:
      # See https://github.com/pi-hole/docker-pi-hole#note-on-capabilities
      # Required if you are using Pi-hole as your DHCP server, else not needed
      - NET_ADMIN
      # Required if you are using Pi-hole as your NTP client to be able to set the host's system time
      - SYS_TIME
      # Optional, if Pi-hole should get some more processing time
      - SYS_NICE
    restart: unless-stopped
    networks:
      mynet:
        ipv4_address: 192.168.4.241
networks:
  mynet:
    external: true

Display More

skullkidrae · Sunday, 12:50 pm

Quote from raulfg3

please create mynet in Compose webGUI First.

how do i do that. is it a file under compose?

skullkidrae · Saturday, 11:05 pm

Quote from ryecoaaron

You shouldn't use a mergerfs pool for your docker storage. Use a normal native Linux filesystem.

ok. i think iv got it working.

skullkidrae · Saturday, 11:03 pm

Quote from chente

If you've repaired Pihole, you've broken OMV. They can't coexist because they both need port 53.

The way to make them coexist is to configure Pihole in a container and use a VLAN. Read here --> https://wiki.omv-extras.org/do…te_a_vlan_pi-hole_adguard
However, this has a limitation: OMV won't be able to use the DNS server provided by Pihole, since the container can't communicate with the host.

ok. iv got omv running again and docker working..... i think. as far as i understand the article is getting me to setup vlan with a copy of my network info. appending config to the pihole docker file allowing it to use the same port on a different ip asif it was a separate device (ip from the vlan not my network) . but i cant get pihole running in docker. when im running it im getting an error <

time="2026-01-10T22:22:25Z" level=warning msg="No services to build"
network mynet declared as external, but could not be found

*** ERROR #1 ***

END OF LINE

█>help

skullkidrae · Saturday, 8:00 pm

Quote from gderf

Save the text to a file and then attach it to your post.

that makes scence. sorry im a total noob to this.

skullkidrae · Saturday, 7:47 pm

omv docker error.txt

skullkidrae · Saturday, 7:34 pm

Code

ID: container_storage_dir
Function: file.directory
Name: /srv/mergerfs/spidernas/docker
Result: True
Comment: Directory /srv/mergerfs/spidernas/docker updated
Started: 18:15:38.613013
Duration: 1.259 ms
Changes:
----------
/srv/mergerfs/spidernas/docker:
----------
mode:
0755
mode:
0755
----------
ID: docker_install_packages
Function: pkg.installed
Result: True
Comment: All specified packages are already installed
Started: 18:15:39.399795
Duration: 32.663 ms
Changes:
----------
ID: configure_etc_docker_dir
Function: file.directory
Name: /etc/docker
Result: True
Comment: The directory /etc/docker is in the correct state
Started: 18:15:39.432607
Duration: 1.014 ms
Changes:
----------
ID: /etc/docker/daemon.json
Function: file.serialize
Result: True
Comment: File /etc/docker/daemon.json is in the correct state
Started: 18:15:39.433732
Duration: 2.713 ms
Changes:
----------
ID: docker
Function: service.running
Result: False
Comment: Running as unit: run-p37516-i37816.scope; invocation ID: 7297b6d30e5342729334c03ec5ee49a2
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xeu docker.service" for details.
Started: 18:15:39.437594
Duration: 180.494 ms
Changes:
----------
ID: common_install_packages
Function: pkg.installed
Result: True
Comment: All specified packages are already installed
Started: 18:15:39.618581
Duration: 9.729 ms
Changes:
----------
ID: /etc/systemd/system/docker.service.d/waitAllMounts.conf
Function: file.managed
Result: True
Comment: File /etc/systemd/system/docker.service.d/waitAllMounts.conf is in the correct state
Started: 18:15:39.628439
Duration: 1.702 ms
Changes:
----------
ID: systemd_daemon_reload
Function: cmd.run
Name: systemctl daemon-reload
Result: True
Comment: State was not run because none of the onchanges reqs changed
Started: 18:15:39.631399
Duration: 0.004 ms
Changes:
----------
ID: configure_compose_scheduled_backup
Function: file.managed
Name: /etc/cron.d/omv-compose-backup
Result: True
Comment: File /etc/cron.d/omv-compose-backup is in the correct state
Started: 18:15:39.631473
Duration: 11.794 ms
Changes:
----------
ID: configure_compose_scheduled_update
Function: file.managed
Name: /etc/cron.d/omv-compose-update
Result: True
Comment: File /etc/cron.d/omv-compose-update is in the correct state
Started: 18:15:39.643417
Duration: 11.255 ms
Changes:
----------
ID: configure_compose_scheduled_prune
Function: file.managed
Name: /etc/cron.d/omv-compose-prune
Result: True
Comment: File /etc/cron.d/omv-compose-prune is in the correct state
Started: 18:15:39.654817
Duration: 11.304 ms
Changes:
----------
ID: configure_compose_scheduled_start
Function: file.managed
Name: /etc/cron.d/omv-compose-start
Result: True
Comment: File /etc/cron.d/omv-compose-start is in the correct state
Started: 18:15:39.666270
Duration: 11.216 ms
Changes:
----------
ID: configure_compose_scheduled_build
Function: file.managed
Name: /etc/cron.d/omv-compose-build
Result: True
Comment: File /etc/cron.d/omv-compose-build is in the correct state
Started: 18:15:39.677627
Duration: 12.242 ms
Changes:
----------
ID: configure_compose_scheduled_stop
Function: file.managed
Name: /etc/cron.d/omv-compose-stop
Result: True
Comment: File /etc/cron.d/omv-compose-stop is in the correct state
Started: 18:15:39.690017
Duration: 11.229 ms
Changes:

Summary for spidernas
-------------
Succeeded: 14 (changed=1)
Failed: 1
-------------
Total states run: 15
Total run time: 305.099 ms
[ERROR ] Command '/bin/systemd-run' failed with return code: 1
[ERROR ] stderr: Running as unit: run-p37516-i37816.scope; invocation ID: 7297b6d30e5342729334c03ec5ee49a2
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xeu docker.service" for details.
[ERROR ] retcode: 1
[ERROR ] Running as unit: run-p37516-i37816.scope; invocation ID: 7297b6d30e5342729334c03ec5ee49a2
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xeu docker.service" for details. in /usr/share/php/openmediavault/system/process.inc:247
Stack trace:
#0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(62): OMV\System\Process->execute()
#1 /usr/share/openmediavault/engined/rpc/config.inc(187): OMV\Engine\Module\ServiceAbstract->deploy()
#2 [internal function]: Engined\Rpc\Config->applyChanges()
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array()
#4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(169): OMV\Rpc\ServiceAbstract->callMethod()
#5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(646): OMV\Rpc\ServiceAbstract->{closure:OMV\Rpc\ServiceAbstract::callMethodBg():155}()
#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(155): OMV\Rpc\ServiceAbstract->execBgProc()
#7 /usr/share/openmediavault/engined/rpc/config.inc(209): OMV\Rpc\ServiceAbstract->callMethodBg()
#8 [internal function]: Engined\Rpc\Config->applyChangesBg()
#9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array()
#10 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod()
#11 /usr/sbin/omv-engined(546): OMV\Rpc\Rpc::call()
#12 {main}

Display More

skullkidrae · Saturday, 7:33 pm

Code

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=; omv-salt deploy run --no-color compose 2>&1' with exit code '1': spidernas:
----------
ID: configure_compose_global_env_file
Function: file.managed
Name: /srv/mergerfs/spidernas/appdata/global.env
Result: True
Comment: File /srv/mergerfs/spidernas/appdata/global.env is in the correct state
Started: 18:15:38.606393
Duration: 6.481 ms
Changes:
----------
ID: container_storage_dir
Function: file.directory
Name: /srv/mergerfs/spidernas/docker
Result: True
Comment: Directory /srv/mergerfs/spidernas/docker updated
Started: 18:15:38.613013
Duration: 1.259 ms
Changes:
----------
/srv/mergerfs/spidernas/docker:
----------
mode:
0755
mode:
0755
----------
ID: docker_install_packages
Function: pkg.installed
Result: True
Comment: All specified packages are already installed
Started: 18:15:39.399795
Duration: 32.663 ms
Changes:
----------
ID: configure_etc_docker_dir
Function: file.directory
Name: /etc/docker
Result: True
Comment: The directory /etc/docker is in the correct state
Started: 18:15:39.432607
Duration: 1.014 ms
Changes:
----------
ID: /etc/docker/daemon.json
Function: file.serialize
Result: True
Comment: File /etc/docker/daemon.json is in the correct state
Started: 18:15:39.433732
Duration: 2.713 ms
Changes:
----------
ID: docker
Function: service.running
Result: False
Comment: Running as unit: run-p37516-i37816.scope; invocation ID: 7297b6d30e5342729334c03ec5ee49a2
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xeu docker.service" for details.
Started: 18:15:39.437594
Duration: 180.494 ms
Changes:
----------
ID: common_install_packages
Function: pkg.installed
Result: True
Comment: All specified packages are already installed
Started: 18:15:39.618581
Duration: 9.729 ms
Changes:
----------
ID: /etc/systemd/system/docker.service.d/waitAllMounts.conf
Function: file.managed
Result: True
Comment: File /etc/systemd/system/docker.service.d/waitAllMounts.conf is in the correct state
Started: 18:15:39.628439
Duration: 1.702 ms
Changes:
----------
ID: systemd_daemon_reload
Function: cmd.run
Name: systemctl daemon-reload
Result: True
Comment: State was not run because none of the onchanges reqs changed
Started: 18:15:39.631399
Duration: 0.004 ms
Changes:
----------
ID: configure_compose_scheduled_backup
Function: file.managed
Name: /etc/cron.d/omv-compose-backup
Result: True
Comment: File /etc/cron.d/omv-compose-backup is in the correct state
Started: 18:15:39.631473
Duration: 11.794 ms
Changes:
----------
ID: configure_compose_scheduled_update
Function: file.managed
Name: /etc/cron.d/omv-compose-update
Result: True
Comment: File /etc/cron.d/omv-compose-update is in the correct state
Started: 18:15:39.643417
Duration: 11.255 ms
Changes:
----------
ID: configure_compose_scheduled_prune
Function: file.managed
Name: /etc/cron.d/omv-compose-prune
Result: True
Comment: File /etc/cron.d/omv-compose-prune is in the correct state
Started: 18:15:39.654817
Duration: 11.304 ms
Changes:
----------
ID: configure_compose_scheduled_start
Function: file.managed
Name: /etc/cron.d/omv-compose-start
Result: True
Comment: File /etc/cron.d/omv-compose-start is in the correct state
Started: 18:15:39.666270
Duration: 11.216 ms
Changes:
----------
ID: configure_compose_scheduled_build
Function: file.managed
Name: /etc/cron.d/omv-compose-build
Result: True
Comment: File /etc/cron.d/omv-compose-build is in the correct state
Started: 18:15:39.677627
Duration: 12.242 ms
Changes:
----------
ID: configure_compose_scheduled_stop
Function: file.managed
Name: /etc/cron.d/omv-compose-stop
Result: True
Comment: File /etc/cron.d/omv-compose-stop is in the correct state
Started: 18:15:39.690017
Duration: 11.229 ms
Changes:

Summary for spidernas
-------------
Succeeded: 14 (changed=1)
Failed: 1
-------------
Total states run: 15
Total run time: 305.099 ms
[ERROR ] Command '/bin/systemd-run' failed with return code: 1
[ERROR ] stderr: Running as unit: run-p37516-i37816.scope; invocation ID: 7297b6d30e5342729334c03ec5ee49a2
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xeu docker.service" for details.
[ERROR ] retcode: 1
[ERROR ] Running as unit: run-p37516-i37816.scope; invocation ID: 7297b6d30e5342729334c03ec5ee49a2
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xeu docker.service" for details.

OMV\ExecException: 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=; omv-salt deploy run --no-color compose 2>&1' with exit code '1': spidernas:
----------
ID: configure_compose_global_env_file
Function: file.managed
Name: /srv/mergerfs/spidernas/appdata/global.env
Result: True
Comment: File /srv/mergerfs/spidernas/appdata/global.env is in the correct state
Started: 18:15:38.606393
Duration: 6.481 ms
Changes:
----------

Display More

skullkidrae · Saturday, 7:16 pm

apprently its too long to post

Posts by skullkidrae

pihole and omv on one pi?

pihole and omv on one pi?

pihole and omv on one pi?

pihole and omv on one pi?

pihole and omv on one pi?

pihole and omv on one pi?

pihole and omv on one pi?

pihole and omv on one pi?

pihole and omv on one pi?

pihole and omv on one pi?

pihole and omv on one pi?

pihole and omv on one pi?

pihole and omv on one pi?

docker setup issues

pihole and omv on one pi?

docker setup issues

docker setup issues

docker setup issues

docker setup issues

docker setup issues