github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-05-07 21:30:36 -05:00
Code Issues 564 Packages Projects Releases 72 Wiki Activity

[GH-ISSUE #1184] Installer error if ipv6 is disabled #8560

New Issue
Closed
opened 2026-04-30 04:32:16 -05:00 by GiteaMirror · 7 comments
GiteaMirror commented 2026-04-30 04:32:16 -05:00
Owner
Copy Link

Originally created by @djlobster on GitHub (Jul 31, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1184

Originally assigned to: @Xentrice on GitHub.

IPv6 is disabled on my VPS. Installer works fine if I say 'no' to starting the containers. If I say 'yes' then it gives me an error about the ipv6 portion because it's not available on my VPS. This also halts the installer so you never get asked about anything after this point like Crowdsec. I did originally comment out the IPv6 portion of the compose file and everything worked fine, I just realized after that it never did actually finish the installer. I tried it again just to be sure and then moved onto inputting 'no'.

=== Starting installation ===
Would you like to install and start the containers? (yes/no) (default: yes): yes
Pulling the container images...
[+] Pulling 3/3
 ✔ pangolin Pulled                                                                                                                                    0.1s 
 ✔ gerbil Pulled                                                                                                                                      0.2s 
 ✔ traefik Pulled                                                                                                                                     0.1s 
Starting containers...
[+] Running 1/1
 ✘ Network pangolin  Error                                                                                                                            0.0s 
failed to create network pangolin: Error response from daemon: Cannot read IPv6 setup for bridge br-9b656c609139: open /proc/sys/net/ipv6/conf/br-9b656c609139/disable_ipv6: no such file or directory
Error:  failed to start containers: exit status 1

After inputting 'no':

=== Starting installation ===
Would you like to install and start the containers? (yes/no) (default: yes): no

=== CrowdSec Install ===
Would you like to install CrowdSec? (yes/no) (default: no): yes
This installer constitutes a minimal viable CrowdSec deployment. CrowdSec will add extra complexity to your Pangolin installation and may not work to the best of its abilities out of the box. Users are expected to implement configuration adjustments on their own to achieve the best security posture. Consult the CrowdSec documentation for detailed configuration instructions.
Are you willing to manage CrowdSec? (yes/no) (default: no): yes
Stopping containers...
Installation complete!

To complete the initial setup, please visit:
https://domain/auth/initial-setup
Originally created by @djlobster on GitHub (Jul 31, 2025). Original GitHub issue: https://github.com/fosrl/pangolin/issues/1184 Originally assigned to: @Xentrice on GitHub. IPv6 is disabled on my VPS. Installer works fine if I say 'no' to starting the containers. If I say 'yes' then it gives me an error about the ipv6 portion because it's not available on my VPS. This also halts the installer so you never get asked about anything after this point like Crowdsec. I did originally comment out the IPv6 portion of the compose file and everything worked fine, I just realized after that it never did actually finish the installer. I tried it again just to be sure and then moved onto inputting 'no'. ``` === Starting installation === Would you like to install and start the containers? (yes/no) (default: yes): yes Pulling the container images... [+] Pulling 3/3 ✔ pangolin Pulled 0.1s ✔ gerbil Pulled 0.2s ✔ traefik Pulled 0.1s Starting containers... [+] Running 1/1 ✘ Network pangolin Error 0.0s failed to create network pangolin: Error response from daemon: Cannot read IPv6 setup for bridge br-9b656c609139: open /proc/sys/net/ipv6/conf/br-9b656c609139/disable_ipv6: no such file or directory Error: failed to start containers: exit status 1 ``` After inputting 'no': ``` === Starting installation === Would you like to install and start the containers? (yes/no) (default: yes): no === CrowdSec Install === Would you like to install CrowdSec? (yes/no) (default: no): yes This installer constitutes a minimal viable CrowdSec deployment. CrowdSec will add extra complexity to your Pangolin installation and may not work to the best of its abilities out of the box. Users are expected to implement configuration adjustments on their own to achieve the best security posture. Consult the CrowdSec documentation for detailed configuration instructions. Are you willing to manage CrowdSec? (yes/no) (default: no): yes Stopping containers... Installation complete! To complete the initial setup, please visit: https://domain/auth/initial-setup ```
GiteaMirror added the needs investigatingconfig labels 2026-04-30 04:32:16 -05:00
GiteaMirror commented 2026-04-30 04:32:18 -05:00
Author
Owner
Copy Link

@Xentrice commented on GitHub (Aug 1, 2025):

This is caused by my pull request #1111
Damn, i was sure i tested everything.
I will create a pull request shortly making the IPv6 optional during installation. I didn't think this was necessary.
Which VPS and OS are you using?

<!-- gh-comment-id:3145041140 --> @Xentrice commented on GitHub (Aug 1, 2025): This is caused by my pull request #1111 Damn, i was sure i tested everything. I will create a pull request shortly making the IPv6 optional during installation. I didn't think this was necessary. Which VPS and OS are you using?
GiteaMirror commented 2026-04-30 04:32:19 -05:00
Author
Owner
Copy Link

@djlobster commented on GitHub (Aug 1, 2025):

I'm using a Netcup VPS with Ubuntu 24.04.2 LTS. I can use IPv6 with my VPS, but I've manually disabled it in the OS and that's why this happened. Would it be easy to put a check in the installer to see if IPv6 is enabled or not and skip that part of the compose file if it's not? Everything works fine as long as I don't try to start the container during install and then remove the IPv6 part of the compose file after the installer finishes.

<!-- gh-comment-id:3145218571 --> @djlobster commented on GitHub (Aug 1, 2025): I'm using a Netcup VPS with Ubuntu 24.04.2 LTS. I _can_ use IPv6 with my VPS, but I've manually disabled it in the OS and that's why this happened. Would it be easy to put a check in the installer to see if IPv6 is enabled or not and skip that part of the compose file if it's not? Everything works fine as long as I don't try to start the container during install and then remove the IPv6 part of the compose file after the installer finishes.
GiteaMirror commented 2026-04-30 04:32:20 -05:00
Author
Owner
Copy Link

@oschwartz10612 commented on GitHub (Aug 1, 2025):

Thanks for taking point @Xentrice !

Did you hard disable in /etc/sysctl.conf? That would make sense if docker is complaining.

<!-- gh-comment-id:3145254681 --> @oschwartz10612 commented on GitHub (Aug 1, 2025): Thanks for taking point @Xentrice ! Did you hard disable in `/etc/sysctl.conf`? That would make sense if docker is complaining.
GiteaMirror commented 2026-04-30 04:32:21 -05:00
Author
Owner
Copy Link

@Xentrice commented on GitHub (Aug 1, 2025):

This is very interesting, provisioning an IPv6 capable server and disabling IPv6 afterwards in the OS is something I specifically tested without problem, although on a hetzner VPS with Debian 12. How did you disable IPv6?
Automatically checking for IPv6 during install could be done ofc, but I'm not sure how to ensure that all edge cases and different distributions are considered as well.
I feel like asking the user during install is the safest bet for now.

<!-- gh-comment-id:3145256028 --> @Xentrice commented on GitHub (Aug 1, 2025): This is very interesting, provisioning an IPv6 capable server and disabling IPv6 afterwards in the OS is something I specifically tested without problem, although on a hetzner VPS with Debian 12. How did you disable IPv6? Automatically checking for IPv6 during install could be done ofc, but I'm not sure how to ensure that all edge cases and different distributions are considered as well. I feel like asking the user during install is the safest bet for now.
GiteaMirror commented 2026-04-30 04:32:23 -05:00
Author
Owner
Copy Link

@djlobster commented on GitHub (Aug 1, 2025):

I have /etc/sysctl.d/99-disable-ipv6.conf set with:

net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1

and in /etc/default/grub I have:

GRUB_CMDLINE_LINUX="ipv6.disable=1"
<!-- gh-comment-id:3145315476 --> @djlobster commented on GitHub (Aug 1, 2025): I have `/etc/sysctl.d/99-disable-ipv6.conf` set with: ``` net.ipv6.conf.all.disable_ipv6 = 1 net.ipv6.conf.default.disable_ipv6 = 1 net.ipv6.conf.lo.disable_ipv6 = 1 ``` and in `/etc/default/grub` I have: ``` GRUB_CMDLINE_LINUX="ipv6.disable=1" ```
GiteaMirror commented 2026-04-30 04:32:24 -05:00
Author
Owner
Copy Link

@crookshanked commented on GitHub (Aug 7, 2025):

Ubuntu 24 CIS disabled ipv6 as well. I encountered an issue with it on install, but changing the ipv6 to false under networks seems to get things moving again.

<!-- gh-comment-id:3162261853 --> @crookshanked commented on GitHub (Aug 7, 2025): Ubuntu 24 CIS disabled ipv6 as well. I encountered an issue with it on install, but changing the ipv6 to false under networks seems to get things moving again.
GiteaMirror commented 2026-04-30 04:32:25 -05:00
Author
Owner
Copy Link

@oschwartz10612 commented on GitHub (Aug 8, 2025):

Hopefully fixed by #1212

<!-- gh-comment-id:3166202523 --> @oschwartz10612 commented on GitHub (Aug 8, 2025): Hopefully fixed by #1212
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
authentication
bug
config
dependencies
docker
documentation
enhancement
good first issue
help wanted
Improvement
Look Into
needs investigating
networking
new feature
non-critical bug
potential bug
pull-request
Mirrored from GitHub Pull Request
 question
reverse proxy
Security
stale
ui
wontfix
No Label config needs investigating
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#8560
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?