Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem with first start wings #4785

Closed
3 tasks done
StarGate88 opened this issue May 23, 2023 · 6 comments
Closed
3 tasks done

Problem with first start wings #4785

StarGate88 opened this issue May 23, 2023 · 6 comments
Labels
not confirmed Report seems plausible but requires additional testing or 3rd part confirmation.

Comments

@StarGate88
Copy link

Current Behavior

Hi,

i have docker server with other applications, but now i need install pterodactyl panel. Problem is trough run wings, it´s write me error

Where cann i specify network address space in pterodactil or wings for docker?

Thank you for response.

Expected Behavior

Run with other applications in docker with choice IP network

Steps to Reproduce

After first installation

Panel Version

1.11.3

Wings Version

1.11.6

Games and/or Eggs Affected

No response

Docker Image

No response

Error Logs

FATAL: [May 23 14:43:45.166] failed to configure docker environment error=Error response from daemon: Pool overlaps with other one on this address space

Stacktrace:
Error response from daemon: Pool overlaps with other one on this address space

Is there an existing issue for this?

  • I have searched the existing issues before opening this issue.
  • I have provided all relevant details, including the specific game and Docker images I am using if this issue is related to running a server.
  • I have checked in the Discord server and believe this is a bug with the software, and not a configuration issue with my specific system.
@StarGate88 StarGate88 added the not confirmed Report seems plausible but requires additional testing or 3rd part confirmation. label May 23, 2023
@parkervcp
Copy link
Member

You need to edit the config.yml to use an address other than 172.18.0.1. This has been covered many times

This is the section you want to edit.

docker:
  network:
    interfaces:
      v4:
        subnet: 172.18.0.0/16
        gateway: 172.18.0.1

@treverehrfurth
Copy link

I'm getting this same issue, only I have verified I am not using any other subnet and it is available.
I have also tried adding a gateway with no luck

@treverehrfurth
Copy link

Although my issue doesn't say when i run the docker compose, it says it runs fine but in portainer it shows the issue in the logs

@lologaby
Copy link

lologaby commented Sep 8, 2024

Well, ive tried multiple subnets and still get this error

@August7337
Copy link

@lologaby @treverehrfurth Did you find something, I have the same issue

`FATAL: [Sep 17 17:28:59.182] failed to configure docker environment error=Error response from daemon: invalid pool request: Pool overlaps with other one on this address space

Stacktrace:
Error response from daemon: invalid pool request: Pool overlaps with other one on this address space`

@August7337
Copy link

@lologaby @treverehrfurth Did you find something, I have the same issue

`FATAL: [Sep 17 17:28:59.182] failed to configure docker environment error=Error response from daemon: invalid pool request: Pool overlaps with other one on this address space

Stacktrace: Error response from daemon: invalid pool request: Pool overlaps with other one on this address space`

I find something on discord

If you can't boot because of overlapping subnet to expand the config, then here's a boilerplate for you to edit
Default wings network docker config template if you are having overlapping networks and can't generate it. Copy it into your config.yml and change the occurrences of 172.18.0.x to something that's not already in use by your other networks. For example, 172.20.0.1

docker:
network:
interface: 172.18.0.1
dns:
- 1.1.1.1
- 1.0.0.1
name: pterodactyl_nw
ispn: false
driver: bridge
network_mode: pterodactyl_nw
is_internal: false
enable_icc: true
interfaces:
v4:
subnet: 172.18.0.0/16
gateway: 172.18.0.1
v6:
subnet: fdba:17c8:6c94::/64
gateway: fdba:17c8:6c94::1011
domainname: ""
registries: {}
tmpfs_size: 100

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
not confirmed Report seems plausible but requires additional testing or 3rd part confirmation.
Projects
None yet
Development

No branches or pull requests

5 participants