rancher: Can't bind on 127.0.0.1

@zot24 I found a workaround to that by adding in the edit page of the host the ip: 127.0.0.1. I really don’t know if this is the expected behavior but it works for me now.

Any updates guys? Binding on localhost (127.0.0.1) should be a simple feature since 0.0.0.0 is working by default. There are a lot of reasons here (security for example) and maybe the feature can be extended to binding on a specific IP on a host with multiple LANs to cover all of the use cases. Cheers!

So i found a workaround for Rancher 1.6.15 you can expose ports to 127.0.0.1 when you set a specific host under the scheduling tab. So i guess this will be useless for multihost setups.

Tried your compose file on 1.6.13 with a different port because 80 is already bound in my host

Unfortunately the result is this:

i.e. service cannot be started with these logs

Maybe I’m doing something wrong

Any updates on this? Issue seems to be still existing on 1.16.10. We are running a service that needs to proxied on the host but this exposes the service to the internet.

I’m experiencing a similar issue where I got the following configuration (that was working on Rancher 1.2.2)

version: 2
services:
  fluentd:
    image: localhost/fluentd
    env_file: .env
    ports:
      - "127.0.0.1:24224:24224"

But with Rancher Server 1.6.7 I just get the following error

 Upgrading (Failed to allocate instance [container:1i126]: Bad instance [container:1i126] in state [error]: Allocation failed: No healthy hosts meet the resource constraints: [127.0.0.1:24224:24224/tcp portReservation, instanceReservation: 1])
Type: