API Server Docker Container Issues

[davida72]

I can't get the API Server working. From the dockerfile it looks like port 8080 is hard coded. No?

At any rate, this is what I see in the logs. I'm unable to access it via a browser.

WARNING:  ASGI app factory detected. Using it, but please consider setting the --factory flag explicitly.
INFO:     Started server process [1]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     Uvicorn running on http://0.0.0.0:8080 (Press CTRL+C to quit)

[My-Random-Thoughts]

I have the same warning, it can be ignored. My docker is working fine.

What error messages are you getting?
What are you trying?

[davida72]

Edit: this wasn't the fix so ignore this post!

I figured it out.

I needed to build the container before I deployed it. Previously I had just added the docker-compose, which pulls robbrad182/uk-bin-collection:latest but that doesn't create all the requirements.

Shouldn't the docker container at robbrad182/uk-bin-collection:latest be everything needed for the container without needing a rebuild? I see that the documentation describes a necessary rebuild, but that wasn't a process I was familiar with.

[My-Random-Thoughts]

It should.
I posted my working compose file here - #1288

[davida72]

SOLVED!

Port 8080 is already used on my computer so my docker-compose used a different port.

    ports:
      - 9095:9095

But I realise the internal port needs to be 8080, so it should instead look like this.

    ports:
      - 9095:8080

And that the official sample docker-compose.yml file could be made clearer.

From

    ports:
      - "8080:8080"  # Adjust the ports as needed

To

    ports:
      - "8080:8080"  # Adjust the second (container) port as needed

Since 8080 must always remain the host port I think.

[robbrad]

SOLVED!

Port 8080 is already used on my computer so my docker-compose used a different port.

    ports:

      - 9095:9095

But I realise the internal port needs to be 8080, so it should instead look like this.

    ports:

      - 9095:8080

And that the official sample docker-compose.yml file could be made clearer.

From

    ports:

      - "8080:8080"  # Adjust the ports as needed

To

    ports:

      - "8080:8080"  # Adjust the second (container) port as needed

Since 8080 must always remain the host port I think.

Happy for improvements do the comment, however I do want to call out this is how Docker works when using bridge network mode.

You host a service on a port on the container and map it to the host port.

See https://www.warp.dev/terminus/docker-compose-port-mapping

[davida72]

Understood. There are a few aspects of this project that are a little bit outside my field of expertise, so I'm describing newbie mistakes.

But at this point I have it working as a container, as a Home Assistant plugin and as a command line.