Pugnacious

The network i'm using is a bridged network that links back to the main vlan i'm using putting the docker containers directly on it instead of being filtered through the host. Here's what that section of the file looks like now. If i modify it to use the host instead of the custom docker, it just changes it back on start. I'm clearly missing something else. docker: network: interface: 10.16.5.1 dns: - 1.1.1.1 - 1.0.0.1 name: pelican_net ispn: false IPv6: false driver: bridge network_mode: pelican_net is_internal: false enable_icc: true network_mtu: 1500 interfaces: v4: subnet: 10.16.5.0/24 gateway: 10.16.5.1 v6: subnet: fd00:10:16:5::/64 gateway: fd00:10:16:5::/64 domainname: "" registries: {} tmpfs_size: 100 container_pid_limit: 512 installer_limits: memory: 1024 cpu: 100 overhead: override: false default_multiplier: 1.05 multipliers: {} use_performant_inspect: true userns_mode: "" system_ips: [] log_config: type: local config: compress: "false" max-file: "1" max-size: 5m mode: non-blocking

I see. Now that i look at the new file, i see the docker setup. What's the best way to modify this to put it on my network? docker mode host?

The node is connected to the panel. Is it supposed to modify the config after it's linked? I pulled the original one from the panel.

Mine looks like this(stripped out the token): debug: false uuid: 5ff9186f-5c4a-4202-9538-d37c1f7db8be token_id: token: api: host: 0.0.0.0 port: 8080 ssl: enabled: false cert: /etc/letsencrypt/live/192.168.10.7/fullchain.pem key: /etc/letsencrypt/live/192.168.10.7/privkey.pem upload_limit: 256 system: data: /mnt/user/appdata/pelican-wing/data sftp: bind_port: 2022 allowed_mounts: [] remote: 'http://192.168.10.4'

For Pelican, I've been trying to get it working using a custom bridged network and giving the panel and wing their own IP addresses. I can't seem to see the game servers on the network though. I'm guessing it sets up a pelican docker network for internal use and isn't exposing the ports correctly. What's the best way to sort that out?

Thanks bud!

I too am getting this error. I did some checking from inside the docker container and indeed the awk command isn't present. perhaps the new version is missing that in the build? Did some more checking. logged into the docker by using the command: docker exec -it binhex-sabnzbdvpn bash then used the command: pacman -S awk accepted the file setup and restarted the docker. a more permanent fix would be to edit the startup script build/root/install.sh line 22: pacman_packages="git python2 python2-pyopenssl python2-feedparser p7zip ipcalc awk"