Hi @Tristan107, only port 80 is exposed through the Public Device URL (see the relevant docs), that is a technical limitation of the forwarding, but we’re checking whether this can be expanded (but that’s the current status)
When
That statement does not mention the Public Device URLs, the exposed ports are on the device itself, i.e. exposed on the network the device is accessible on (usually the LAN). Meaning: if you open a port in your application, any port, resinOS does not have any restriction on those ports.
Regarding the autorestart, “docker cloud” is not really the relevant thing, the correct respective docker setting is the docker run --restart documentation and for Docker 1.10.3 (see it here). The restart in our case is done by the resin-supervisor, and controlled by the RESIN_APP_RESTART_POLICY device configuration variable (and RESIN_APP_RESTART_RETRIES):
RESIN_APP_RESTART_POLICY can take one of the valid values defined by docker run --restart, that are: no, always, on-failure, unless-stopped. If the selection is on-failure, then it will try the restart as many times as RESIN_APP_RESTART_RETRIES defines it. The restart times are exactly the same as any other docker instance would do with the same settings.
Unfortunately this is not well covered in our docs (we will be fixing that), in the meantime this should be most of it.