Docker Container

[kenkendk]

@Pampa_Party

i understand what --webservice-interface=any mean. what i don´t understand is why the container always starts with --webservice-interface=any and why i can´t change it. So probably you’re not getting my question and i don´t get your point as i mentioned before.

Just to clarify:
The environment variable:

DUPLICATI__WEBSERVICE_INTERFACE=any

Is the same as setting the commandline argument:

--webservice-interface=any

The environment variable way is (usually) easier with Docker.

@Pampa_Party

but after this my container was restarting every 5 seconds and the gui acces was gone. So maybe its just how the container is build and works, with DUPLICATI__WEBSERVICE_INTERFACE=any? And the container needs it to function properly?

I think you are correct here, and I was wrong. You need any for it to work.

The network inside the Docker container can actually be private. So if Duplicati only listens to loopback (aka aka 127.0.0.1), no process outside the container can access it:

Is there a way to expose a docker container port bound to 127.0.0.1 to host?

I don’t know why it is crashing, but you will not be able to connect.

So to recap:

• You need to have the “External access” enabled
• Since this only has effect inside Docker, it should be read as “Allow access from outside the container”
• On the Docker host, you control how the access is further exposed, and here you can limit it to localhost access only

There is nothing Duplicati can do, because the process inside the container cannot (by design) affect things outside.

@Pampa_Party

if you could just answer “So maybe its just how the container is build and works, with DUPLICATI__WEBSERVICE_INTERFACE=any? And the container needs it to function properly?”

Yes.