Docker image with Uvicorn managed by Gunicorn for high-performance FastAPI web applications in Python 3.6 and above with performance auto-tuning. Optionally with Alpine Linux.

Last update: Dec 31, 2022

Overview

Supported tags and respective `Dockerfile` links

Note: Note: There are tags for each build date. If you need to "pin" the Docker image version you use, you can select one of those tags. E.g. tiangolo/uvicorn-gunicorn-fastapi:python3.7-2019-10-15.

uvicorn-gunicorn-fastapi

Docker image with Uvicorn managed by Gunicorn for high-performance FastAPI web applications in Python 3.6 and above with performance auto-tuning. Optionally in a slim version or based on Alpine Linux.

GitHub repo: https://github.com/tiangolo/uvicorn-gunicorn-fastapi-docker

Docker Hub image: https://hub.docker.com/r/tiangolo/uvicorn-gunicorn-fastapi/

Description

FastAPI has shown to be a Python web framework with one of the best performances, as measured by third-party benchmarks, thanks to being based on and powered by Starlette.

The achievable performance is on par with (and in many cases superior to) Go and Node.js frameworks.

This image has an "auto-tuning" mechanism included, so that you can just add your code and get that same high performance automatically. And without making sacrifices.

Technical Details

Uvicorn

Uvicorn is a lightning-fast "ASGI" server.

It runs asynchronous Python web code in a single process.

Gunicorn

You can use Gunicorn to manage Uvicorn and run multiple of these concurrent processes.

That way, you get the best of concurrency and parallelism.

FastAPI

FastAPI is a modern, fast (high-performance), web framework for building APIs with Python 3.6+.

The key features are:

Fast: Very high performance, on par with NodeJS and Go (thanks to Starlette and Pydantic).
Fast to code: Increase the speed to develop features by about 300% to 500% *.
Less bugs: Reduce about 40% of human (developer) induced errors. *
Intuitive: Great editor support. Completion everywhere. Less time debugging.
Easy: Designed to be easy to use and learn. Less time reading docs.
Short: Minimize code duplication. Multiple features from each parameter declaration. Less bugs.
Robust: Get production-ready code. With automatic interactive documentation.
Standards-based: Based on (and fully compatible with) the open standards for APIs: OpenAPI (previously known as Swagger) and JSON Schema.

* estimation based on tests on an internal development team, building production applications.

`tiangolo/uvicorn-gunicorn-fastapi`

This image will set a sensible configuration based on the server it is running on (the amount of CPU cores available) without making sacrifices.

It has sensible defaults, but you can configure it with environment variables or override the configuration files.

There is also a slim version and another one based on Alpine Linux. If you want one of those, use one of the tags from above.

`tiangolo/uvicorn-gunicorn`

This image (tiangolo/uvicorn-gunicorn-fastapi) is based on tiangolo/uvicorn-gunicorn.

That image is what actually does all the work.

This image just installs FastAPI and has the documentation specifically targeted at FastAPI.

If you feel confident about your knowledge of Uvicorn, Gunicorn and ASGI, you can use that image directly.

`tiangolo/uvicorn-gunicorn-starlette`

There is a sibling Docker image: tiangolo/uvicorn-gunicorn-starlette

If you are creating a new Starlette web application and you want to discard all the additional features from FastAPI you should use tiangolo/uvicorn-gunicorn-starlette instead.

Note: FastAPI is based on Starlette and adds several features on top of it. Useful for APIs and other cases: data validation, data conversion, documentation with OpenAPI, dependency injection, security/authentication and others.

How to use

You don't need to clone the GitHub repo. You can use this image as a base image for other images, using this in your Dockerfile:

FROM tiangolo/uvicorn-gunicorn-fastapi:python3.7

COPY ./app /app

It will expect a file at /app/app/main.py.

Or otherwise a file at /app/main.py.

And will expect it to contain a variable app with your FastAPI application.

Then you can build your image from the directory that has your Dockerfile, e.g:

docker build -t myimage ./

Quick Start

Build your Image

Go to your project directory.
Create a Dockerfile with:

FROM tiangolo/uvicorn-gunicorn-fastapi:python3.7

COPY ./app /app

Create an app directory and enter in it.
Create a main.py file with:

from fastapi import FastAPI

app = FastAPI()


@app.get("/")
def read_root():
    return {"Hello": "World"}


@app.get("/items/{item_id}")
def read_item(item_id: int, q: str = None):
    return {"item_id": item_id, "q": q}

You should now have a directory structure like:

.
├── app
│   └── main.py
└── Dockerfile

Go to the project directory (in where your Dockerfile is, containing your app directory).
Build your FastAPI image:

docker build -t myimage .

Run a container based on your image:

docker run -d --name mycontainer -p 80:80 myimage

Now you have an optimized FastAPI server in a Docker container. Auto-tuned for your current server (and number of CPU cores).

Check it

You should be able to check it in your Docker container's URL, for example: http://192.168.99.100/items/5?q=somequery or http://127.0.0.1/items/5?q=somequery (or equivalent, using your Docker host).

You will see something like:

{"item_id": 5, "q": "somequery"}

Interactive API docs

Now you can go to http://192.168.99.100/docs or http://127.0.0.1/docs (or equivalent, using your Docker host).

You will see the automatic interactive API documentation (provided by Swagger UI):

Alternative API docs

And you can also go to http://192.168.99.100/redoc or http://127.0.0.1/redoc(or equivalent, using your Docker host).

You will see the alternative automatic documentation (provided by ReDoc):

Dependencies and packages

You will probably also want to add any dependencies for your app and pin them to a specific version, probably including Uvicorn, Gunicorn, and FastAPI.

This way you can make sure your app always works as expected.

You could install packages with pip commands in your Dockerfile, using a requirements.txt, or even using Poetry.

And then you can upgrade those dependencies in a controlled way, running your tests, making sure that everything works, but without breaking your production application if some new version is not compatible.

Using Poetry

Here's a small example of one of the ways you could install your dependencies making sure you have a pinned version for each package.

Let's say you have a project managed with Poetry, so, you have your package dependencies in a file pyproject.toml. And possibly a file poetry.lock.

Then you could have a Dockerfile like:

FROM tiangolo/uvicorn-gunicorn-fastapi:python3.7

# Install Poetry
RUN curl -sSL https://raw.githubusercontent.com/python-poetry/poetry/master/get-poetry.py | POETRY_HOME=/opt/poetry python && \
    cd /usr/local/bin && \
    ln -s /opt/poetry/bin/poetry && \
    poetry config virtualenvs.create false

# Copy using poetry.lock* in case it doesn't exist yet
COPY ./app/pyproject.toml ./app/poetry.lock* /app/

RUN poetry install --no-root --no-dev

COPY ./app /app

That will:

Install poetry and configure it for running inside of the Docker container.
Copy your application requirements.
- Because it uses ./app/poetry.lock* (ending with a *), it won't crash if that file is not available yet.
Install the dependencies.
Then copy your app code.

It's important to copy the app code after installing the dependencies, that way you can take advantage of Docker's cache. That way it won't have to install everything from scratch every time you update your application files, only when you add new dependencies.

This also applies for any other way you use to install your dependencies. If you use a requirements.txt, copy it alone and install all the dependencies on the top of the Dockerfile, and add your app code after it.

Advanced usage

Environment variables

These are the environment variables that you can set in the container to configure it and their default values:

`MODULE_NAME`

The Python "module" (file) to be imported by Gunicorn, this module would contain the actual application in a variable.

By default:

app.main if there's a file /app/app/main.py or
main if there's a file /app/main.py

For example, if your main file was at /app/custom_app/custom_main.py, you could set it like:

docker run -d -p 80:80 -e MODULE_NAME="custom_app.custom_main" myimage

`VARIABLE_NAME`

The variable inside of the Python module that contains the FastAPI application.

By default:

app

For example, if your main Python file has something like:

from fastapi import FastAPI

api = FastAPI()


@api.get("/")
def read_root():
    return {"Hello": "World"}

In this case api would be the variable with the FastAPI application. You could set it like:

docker run -d -p 80:80 -e VARIABLE_NAME="api" myimage

`APP_MODULE`

The string with the Python module and the variable name passed to Gunicorn.

By default, set based on the variables MODULE_NAME and VARIABLE_NAME:

app.main:app or
main:app

You can set it like:

docker run -d -p 80:80 -e APP_MODULE="custom_app.custom_main:api" myimage

`GUNICORN_CONF`

The path to a Gunicorn Python configuration file.

By default:

/app/gunicorn_conf.py if it exists
/app/app/gunicorn_conf.py if it exists
/gunicorn_conf.py (the included default)

You can set it like:

docker run -d -p 80:80 -e GUNICORN_CONF="/app/custom_gunicorn_conf.py" myimage

You can use the config file from the base image as a starting point for yours.

`WORKERS_PER_CORE`

This image will check how many CPU cores are available in the current server running your container.

It will set the number of workers to the number of CPU cores multiplied by this value.

By default:

You can set it like:

docker run -d -p 80:80 -e WORKERS_PER_CORE="3" myimage

If you used the value 3 in a server with 2 CPU cores, it would run 6 worker processes.

You can use floating point values too.

So, for example, if you have a big server (let's say, with 8 CPU cores) running several applications, and you have a FastAPI application that you know won't need high performance. And you don't want to waste server resources. You could make it use 0.5 workers per CPU core. For example:

docker run -d -p 80:80 -e WORKERS_PER_CORE="0.5" myimage

In a server with 8 CPU cores, this would make it start only 4 worker processes.

Note: By default, if WORKERS_PER_CORE is 1 and the server has only 1 CPU core, instead of starting 1 single worker, it will start 2. This is to avoid bad performance and blocking applications (server application) on small machines (server machine/cloud/etc). This can be overridden using WEB_CONCURRENCY.

`MAX_WORKERS`

Set the maximum number of workers to use.

You can use it to let the image compute the number of workers automatically but making sure it's limited to a maximum.

This can be useful, for example, if each worker uses a database connection and your database has a maximum limit of open connections.

By default it's not set, meaning that it's unlimited.

You can set it like:

docker run -d -p 80:80 -e MAX_WORKERS="24" myimage

This would make the image start at most 24 workers, independent of how many CPU cores are available in the server.

`WEB_CONCURRENCY`

Override the automatic definition of number of workers.

By default:

Set to the number of CPU cores in the current server multiplied by the environment variable WORKERS_PER_CORE. So, in a server with 2 cores, by default it will be set to 2.

You can set it like:

docker run -d -p 80:80 -e WEB_CONCURRENCY="2" myimage

This would make the image start 2 worker processes, independent of how many CPU cores are available in the server.

`HOST`

The "host" used by Gunicorn, the IP where Gunicorn will listen for requests.

It is the host inside of the container.

So, for example, if you set this variable to 127.0.0.1, it will only be available inside the container, not in the host running it.

It's is provided for completeness, but you probably shouldn't change it.

By default:

0.0.0.0

`PORT`

The port the container should listen on.

If you are running your container in a restrictive environment that forces you to use some specific port (like 8080) you can set it with this variable.

By default:

80

You can set it like:

docker run -d -p 80:8080 -e PORT="8080" myimage

`BIND`

The actual host and port passed to Gunicorn.

By default, set based on the variables HOST and PORT.

So, if you didn't change anything, it will be set by default to:

0.0.0.0:80

You can set it like:

docker run -d -p 80:8080 -e BIND="0.0.0.0:8080" myimage

`LOG_LEVEL`

The log level for Gunicorn.

One of:

debug
info
warning
error
critical

By default, set to info.

If you need to squeeze more performance sacrificing logging, set it to warning, for example:

You can set it like:

docker run -d -p 80:8080 -e LOG_LEVEL="warning" myimage

`WORKER_CLASS`

The class to be used by Gunicorn for the workers.

By default, set to uvicorn.workers.UvicornWorker.

The fact that it uses Uvicorn is what allows using ASGI frameworks like FastAPI, and that is also what provides the maximum performance.

You probably shouldn't change it.

But if for some reason you need to use the alternative Uvicorn worker: uvicorn.workers.UvicornH11Worker you can set it with this environment variable.

You can set it like:

docker run -d -p 80:8080 -e WORKER_CLASS="uvicorn.workers.UvicornH11Worker" myimage

`TIMEOUT`

Workers silent for more than this many seconds are killed and restarted.

Read more about it in the Gunicorn docs: timeout.

By default, set to 120.

Notice that Uvicorn and ASGI frameworks like FastAPI are async, not sync. So it's probably safe to have higher timeouts than for sync workers.

You can set it like:

docker run -d -p 80:8080 -e TIMEOUT="20" myimage

`KEEP_ALIVE`

The number of seconds to wait for requests on a Keep-Alive connection.

Read more about it in the Gunicorn docs: keepalive.

By default, set to 2.

You can set it like:

docker run -d -p 80:8080 -e KEEP_ALIVE="20" myimage

`GRACEFUL_TIMEOUT`

Timeout for graceful workers restart.

Read more about it in the Gunicorn docs: graceful-timeout.

By default, set to 120.

You can set it like:

docker run -d -p 80:8080 -e GRACEFUL_TIMEOUT="20" myimage

`ACCESS_LOG`

The access log file to write to.

By default "-", which means stdout (print in the Docker logs).

If you want to disable ACCESS_LOG, set it to an empty value.

For example, you could disable it with:

docker run -d -p 80:8080 -e ACCESS_LOG= myimage

`ERROR_LOG`

The error log file to write to.

By default "-", which means stderr (print in the Docker logs).

If you want to disable ERROR_LOG, set it to an empty value.

For example, you could disable it with:

docker run -d -p 80:8080 -e ERROR_LOG= myimage

`GUNICORN_CMD_ARGS`

Any additional command line settings for Gunicorn can be passed in the GUNICORN_CMD_ARGS environment variable.

Read more about it in the Gunicorn docs: Settings.

These settings will have precedence over the other environment variables and any Gunicorn config file.

For example, if you have a custom TLS/SSL certificate that you want to use, you could copy them to the Docker image or mount them in the container, and set --keyfile and --certfile to the location of the files, for example:

docker run -d -p 80:8080 -e GUNICORN_CMD_ARGS="--keyfile=/secrets/key.pem --certfile=/secrets/cert.pem" -e PORT=443 myimage

Note: instead of handling TLS/SSL yourself and configuring it in the container, it's recommended to use a "TLS Termination Proxy" like Traefik. You can read more about it in the FastAPI documentation about HTTPS.

`PRE_START_PATH`

The path where to find the pre-start script.

By default, set to /app/prestart.sh.

You can set it like:

docker run -d -p 80:8080 -e PRE_START_PATH="/custom/script.sh" myimage

Custom Gunicorn configuration file

The image includes a default Gunicorn Python config file at /gunicorn_conf.py.

It uses the environment variables declared above to set all the configurations.

You can override it by including a file in:

/app/gunicorn_conf.py
/app/app/gunicorn_conf.py
/gunicorn_conf.py

Custom `/app/prestart.sh`

If you need to run anything before starting the app, you can add a file prestart.sh to the directory /app. The image will automatically detect and run it before starting everything.

For example, if you want to add Alembic SQL migrations (with SQLALchemy), you could create a ./app/prestart.sh file in your code directory (that will be copied by your Dockerfile) with:

#! /usr/bin/env bash

# Let the DB start
sleep 10;
# Run migrations
alembic upgrade head

and it would wait 10 seconds to give the database some time to start and then run that alembic command.

If you need to run a Python script before starting the app, you could make the /app/prestart.sh file run your Python script, with something like:

#! /usr/bin/env bash

# Run custom Python script before starting
python /app/my_custom_prestart_script.py

You can customize the location of the prestart script with the environment variable PRE_START_PATH described above.

Development live reload

The default program that is run is at /start.sh. It does everything described above.

There's also a version for development with live auto-reload at:

/start-reload.sh

Details

For development, it's useful to be able to mount the contents of the application code inside of the container as a Docker "host volume", to be able to change the code and test it live, without having to build the image every time.

In that case, it's also useful to run the server with live auto-reload, so that it re-starts automatically at every code change.

The additional script /start-reload.sh runs Uvicorn alone (without Gunicorn) and in a single process.

It is ideal for development.

Usage

For example, instead of running:

docker run -d -p 80:80 myimage

You could run:

docker run -d -p 80:80 -v $(pwd):/app myimage /start-reload.sh

-v $(pwd):/app: means that the directory $(pwd) should be mounted as a volume inside of the container at /app.
- $(pwd): runs pwd ("print working directory") and puts it as part of the string.
/start-reload.sh: adding something (like /start-reload.sh) at the end of the command, replaces the default "command" with this one. In this case, it replaces the default (/start.sh) with the development alternative /start-reload.sh.

Development live reload - Technical Details

As /start-reload.sh doesn't run with Gunicorn, any of the configurations you put in a gunicorn_conf.py file won't apply.

But these environment variables will work the same as described above:

MODULE_NAME
VARIABLE_NAME
APP_MODULE
HOST
PORT
LOG_LEVEL

Tests

All the image tags, configurations, environment variables and application options are tested.

Release Notes

Latest Changes

👷 Add latest-changes GitHub action, update issue-manager, add funding. PR #70 by @tiangolo.

0.6.0

Add docs about installing and pinning dependencies. PR #41.
Add slim version. PR #40.
Update and refactor bringing all the new features from the base image. Includes:
- Centralize, simplify, and deduplicate code and setup
- Move CI to GitHub actions
- Add Python 3.8 (and Alpine)
- Add new configs and docs:
  - WORKER_CLASS
  - TIMEOUT
  - KEEP_ALIVE
  - GRACEFUL_TIMEOUT
  - ACCESS_LOG
  - ERROR_LOG
  - GUNICORN_CMD_ARGS
  - MAX_WORKERS
- PR #39.
Disable pip cache during installation. PR #38.
Migrate local development from Pipenv to Poetry. PR #34.
Add docs for custom PRE_START_PATH env var. PR #33.

0.5.0

Refactor tests to use env vars and add image tags for each build date, like tiangolo/uvicorn-gunicorn-fastapi:python3.7-2019-10-15. PR #17.
Upgrade Travis. PR #9.

0.4.0

Add support for live auto-reload with an additional custom script /start-reload.sh, check the updated documentation. PR #6 in parent image.

0.3.0

Set WORKERS_PER_CORE by default to 1, as it shows to have the best performance on benchmarks.
Make the default web concurrency, when WEB_CONCURRENCY is not set, to a minimum of 2 workers. This is to avoid bad performance and blocking applications (server application) on small machines (server machine/cloud/etc). This can be overridden using WEB_CONCURRENCY. This applies for example in the case where WORKERS_PER_CORE is set to 1 (the default) and the server has only 1 CPU core. PR #6 and PR #5 in parent image.

0.2.0

Make /start.sh run independently, reading and generating used default environment variables. And remove /entrypoint.sh as it doesn't modify anything in the system, only reads environment variables. PR #4 in parent image.

0.1.0

Add support for /app/prestart.sh.

License

This project is licensed under the terms of the MIT license.

Comments

[QUESTION] How to do logging in a FastApi container, any logging does not appear
Description I have another project that utilizes fast api using gunicorn running uvicorn workers and supervisor to keep the api up. Recently I came across the issue that none of my logs from files that are not the fast api app are coming through. Initially I tried making an adhoc script to see if it works as well as changing the levels of the logging. I only had success if I set the logging to be at the DEBUG level.

I put together another small project to test out if I would run into this problem with a clean slate and I still couldn't get logging working with a standard

import logging log = logging.getLogger(__name__) log.setLevel(logging.INFO) log.info('help!')

Other steps I took was chmod-ing the /var/log/ directory in case it was a permissions issue but I had no luck. Has anyone else ran into this or have recommendations on how they implemented logging?

Additional context For context I put up the testing repo here: https://github.com/PunkDork21/fastapi-git-test Testing it would be like:

docker-compose up -d docker exec -it git-test_web_1 bash python3 ./appy.py

The most of the files are similar to what I have in my real project
question answered
opened by PunkDork21 52
Providing an ARM build?
I am trying to host my FastAPI project on a Raspberry Pi and get the following error every time I hit a RUN: standard_init_linux.go:190: exec user process caused "exec format error"

A little bit of research led me to believe that I need an ARM-image to base my project on, is there anything planned?

My Dockerfile:

# use FastAPI quick-deploy FROM tiangolo/uvicorn-gunicorn:python3.7-alpine3.8 # copy whole installation (minus dockerignore) COPY ./app /app # install additional dependencies COPY ./requirements.txt requirements.txt RUN pip install -r requirements.txt # entrypoints are managed by FastAPI
opened by ModischFabrications 18

Server crashes in production but not in development

I'm sending 217 calls with a 797KB payload each to a FastAPI endpoint. When I run the project with /start-reload.sh it works great. When I run it in production, I get [CRITICAL] WORKER TIMEOUT. I'm assuming this is related to gunicorn. I've read that, under non-async circumstances, worker_class='gevent' might fix the issue, however, in this case the project uses worker_class: uvicorn.workers.UvicornWorker

Any ideas?

Thanks!

$ docker logs -f 0f011d4e9f2b
Checking for script in /app/prestart.sh
There is no script /app/prestart.sh
{"loglevel": "debug", "workers": 4, "bind": "0.0.0.0:80", "workers_per_core": 1.0, "host": "0.0.0.0", "port": "80"}
[2019-04-04 13:45:53 +0000] [1] [DEBUG] Current configuration:
  config: /app/gunicorn_conf.py
  bind: ['0.0.0.0:80']
  backlog: 2048
  workers: 4
  worker_class: uvicorn.workers.UvicornWorker
  threads: 1
  worker_connections: 1000
  max_requests: 0
  max_requests_jitter: 0
  timeout: 30
  graceful_timeout: 30
  keepalive: 120
  limit_request_line: 4094
  limit_request_fields: 100
  limit_request_field_size: 8190
  reload: False
  reload_engine: auto
  reload_extra_files: []
  spew: False
  check_config: False
  preload_app: False
  sendfile: None
  reuse_port: False
  chdir: /app
  daemon: False
  raw_env: []
  pidfile: None
  worker_tmp_dir: None
  user: 0
  group: 0
  umask: 0
  initgroups: False
  tmp_upload_dir: None
  secure_scheme_headers: {'X-FORWARDED-PROTOCOL': 'ssl', 'X-FORWARDED-PROTO': 'https', 'X-FORWARDED-SSL': 'on'}
  forwarded_allow_ips: ['127.0.0.1']
  accesslog: None
  disable_redirect_access_to_syslog: False
  access_log_format: %(h)s %(l)s %(u)s %(t)s "%(r)s" %(s)s %(b)s "%(f)s" "%(a)s"
  errorlog: -
  loglevel: debug
  capture_output: False
  logger_class: gunicorn.glogging.Logger
  logconfig: None
  logconfig_dict: {}
  syslog_addr: udp://localhost:514
  syslog: False
  syslog_prefix: None
  syslog_facility: user
  enable_stdio_inheritance: False
  statsd_host: None
  statsd_prefix: 
  proc_name: None
  default_proc_name: api:app
  pythonpath: None
  paste: None
  on_starting: <function OnStarting.on_starting at 0x7feee3f1ce18>
  on_reload: <function OnReload.on_reload at 0x7feee3f1cf28>
  when_ready: <function WhenReady.when_ready at 0x7feee3f320d0>
  pre_fork: <function Prefork.pre_fork at 0x7feee3f321e0>
  post_fork: <function Postfork.post_fork at 0x7feee3f322f0>
  post_worker_init: <function PostWorkerInit.post_worker_init at 0x7feee3f32400>
  worker_int: <function WorkerInt.worker_int at 0x7feee3f32510>
  worker_abort: <function WorkerAbort.worker_abort at 0x7feee3f32620>
  pre_exec: <function PreExec.pre_exec at 0x7feee3f32730>
  pre_request: <function PreRequest.pre_request at 0x7feee3f32840>
  post_request: <function PostRequest.post_request at 0x7feee3f328c8>
  child_exit: <function ChildExit.child_exit at 0x7feee3f329d8>
  worker_exit: <function WorkerExit.worker_exit at 0x7feee3f32ae8>
  nworkers_changed: <function NumWorkersChanged.nworkers_changed at 0x7feee3f32bf8>
  on_exit: <function OnExit.on_exit at 0x7feee3f32d08>
  proxy_protocol: False
  proxy_allow_ips: ['127.0.0.1']
  keyfile: None
  certfile: None
  ssl_version: 2
  cert_reqs: 0
  ca_certs: None
  suppress_ragged_eofs: True
  do_handshake_on_connect: False
  ciphers: TLSv1
  raw_paste_global_conf: []
[2019-04-04 13:45:53 +0000] [1] [INFO] Starting gunicorn 19.9.0
[2019-04-04 13:45:53 +0000] [1] [DEBUG] Arbiter booted
[2019-04-04 13:45:53 +0000] [1] [INFO] Listening at: http://0.0.0.0:80 (1)
[2019-04-04 13:45:53 +0000] [1] [INFO] Using worker: uvicorn.workers.UvicornWorker
[2019-04-04 13:45:53 +0000] [8] [INFO] Booting worker with pid: 8
[2019-04-04 13:45:53 +0000] [9] [INFO] Booting worker with pid: 9
WARNING:root:email-validator not installed, email fields will be treated as str.
To install, run: pip install email-validator
[2019-04-04 13:45:53 +0000] [11] [INFO] Booting worker with pid: 11
[2019-04-04 13:45:53 +0000] [12] [INFO] Booting worker with pid: 12
[2019-04-04 13:45:53 +0000] [1] [DEBUG] 4 workers
WARNING:root:email-validator not installed, email fields will be treated as str.
To install, run: pip install email-validator
WARNING:root:email-validator not installed, email fields will be treated as str.
To install, run: pip install email-validator
WARNING:root:email-validator not installed, email fields will be treated as str.
To install, run: pip install email-validator
[2019-04-04 13:45:55 +0000] [12] [INFO] Started server process [12]
[2019-04-04 13:45:55 +0000] [11] [INFO] Started server process [11]
[2019-04-04 13:45:55 +0000] [12] [INFO] Waiting for application startup.
[2019-04-04 13:45:55 +0000] [11] [INFO] Waiting for application startup.
[2019-04-04 13:45:55 +0000] [8] [INFO] Started server process [8]
[2019-04-04 13:45:55 +0000] [9] [INFO] Started server process [9]
[2019-04-04 13:45:55 +0000] [8] [INFO] Waiting for application startup.
[2019-04-04 13:45:55 +0000] [9] [INFO] Waiting for application startup.
[2019-04-04 13:49:30 +0000] [11] [DEBUG] ('172.18.0.1', 41826) - Connected
[2019-04-04 13:49:30 +0000] [11] [DEBUG] ('172.18.0.1', 41830) - Connected
[2019-04-04 13:49:30 +0000] [12] [DEBUG] ('172.18.0.1', 41828) - Connected
[2019-04-04 13:49:30 +0000] [9] [DEBUG] ('172.18.0.1', 41832) - Connected
[2019-04-04 13:49:30 +0000] [9] [DEBUG] ('172.18.0.1', 41834) - Connected
[2019-04-04 13:49:31 +0000] [9] [DEBUG] ('172.18.0.1', 41836) - Connected
[2019-04-04 13:49:31 +0000] [9] [DEBUG] ('172.18.0.1', 41838) - Connected
[2019-04-04 13:49:31 +0000] [9] [DEBUG] ('172.18.0.1', 41840) - Connected
[2019-04-04 13:49:31 +0000] [9] [DEBUG] ('172.18.0.1', 41842) - Connected
[2019-04-04 13:49:31 +0000] [9] [DEBUG] ('172.18.0.1', 41844) - Connected
[2019-04-04 13:49:31 +0000] [9] [DEBUG] ('172.18.0.1', 41848) - Connected
[2019-04-04 13:49:31 +0000] [9] [DEBUG] ('172.18.0.1', 41850) - Connected
[2019-04-04 13:49:31 +0000] [9] [DEBUG] ('172.18.0.1', 41852) - Connected
[2019-04-04 13:49:31 +0000] [9] [DEBUG] ('172.18.0.1', 41854) - Connected
[2019-04-04 13:49:31 +0000] [9] [DEBUG] ('172.18.0.1', 41856) - Connected
[2019-04-04 13:49:31 +0000] [9] [DEBUG] ('172.18.0.1', 41858) - Connected
[2019-04-04 13:49:31 +0000] [9] [DEBUG] ('172.18.0.1', 41860) - Connected
[2019-04-04 13:49:31 +0000] [9] [DEBUG] ('172.18.0.1', 41862) - Connected
[2019-04-04 13:49:31 +0000] [9] [DEBUG] ('172.18.0.1', 41864) - Connected
[2019-04-04 13:49:31 +0000] [9] [DEBUG] ('172.18.0.1', 41866) - Connected
[2019-04-04 13:49:31 +0000] [9] [DEBUG] ('172.18.0.1', 41868) - Connected
[2019-04-04 13:49:31 +0000] [8] [DEBUG] ('172.18.0.1', 41846) - Connected
[2019-04-04 13:49:31 +0000] [8] [DEBUG] ('172.18.0.1', 41876) - Connected
[2019-04-04 13:49:31 +0000] [8] [DEBUG] ('172.18.0.1', 41878) - Connected
[2019-04-04 13:49:31 +0000] [8] [DEBUG] ('172.18.0.1', 41880) - Connected
[2019-04-04 13:49:31 +0000] [11] [DEBUG] ('172.18.0.1', 41874) - Connected
[2019-04-04 13:49:31 +0000] [9] [DEBUG] ('172.18.0.1', 41870) - Connected
[2019-04-04 13:49:31 +0000] [9] [DEBUG] ('172.18.0.1', 41872) - Connected
[2019-04-04 13:49:31 +0000] [12] [DEBUG] ('172.18.0.1', 41882) - Connected
[2019-04-04 13:49:31 +0000] [11] [DEBUG] ('172.18.0.1', 41884) - Connected
[2019-04-04 13:49:31 +0000] [11] [DEBUG] ('172.18.0.1', 41888) - Connected
[2019-04-04 13:49:31 +0000] [11] [DEBUG] ('172.18.0.1', 41892) - Connected
[2019-04-04 13:49:31 +0000] [11] [DEBUG] ('172.18.0.1', 41886) - Connected
[2019-04-04 13:49:31 +0000] [11] [DEBUG] ('172.18.0.1', 41894) - Connected
[2019-04-04 13:49:31 +0000] [11] [DEBUG] ('172.18.0.1', 41896) - Connected
[2019-04-04 13:49:31 +0000] [11] [DEBUG] ('172.18.0.1', 41898) - Connected
[2019-04-04 13:49:31 +0000] [11] [DEBUG] ('172.18.0.1', 41900) - Connected
[2019-04-04 13:49:31 +0000] [9] [DEBUG] ('172.18.0.1', 41904) - Connected
[2019-04-04 13:49:31 +0000] [9] [DEBUG] ('172.18.0.1', 41906) - Connected
[2019-04-04 13:49:31 +0000] [9] [DEBUG] ('172.18.0.1', 41908) - Connected
[2019-04-04 13:49:31 +0000] [9] [DEBUG] ('172.18.0.1', 41912) - Connected
[2019-04-04 13:49:31 +0000] [12] [DEBUG] ('172.18.0.1', 41902) - Connected
[2019-04-04 13:49:31 +0000] [12] [DEBUG] ('172.18.0.1', 41910) - Connected
[2019-04-04 13:49:31 +0000] [12] [DEBUG] ('172.18.0.1', 41914) - Connected
[2019-04-04 13:49:31 +0000] [12] [DEBUG] ('172.18.0.1', 41916) - Connected
[2019-04-04 13:49:31 +0000] [12] [DEBUG] ('172.18.0.1', 41920) - Connected
[2019-04-04 13:49:31 +0000] [12] [DEBUG] ('172.18.0.1', 41922) - Connected
[2019-04-04 13:49:31 +0000] [12] [DEBUG] ('172.18.0.1', 41924) - Connected
[2019-04-04 13:49:31 +0000] [12] [DEBUG] ('172.18.0.1', 41926) - Connected
[2019-04-04 13:49:31 +0000] [12] [DEBUG] ('172.18.0.1', 41928) - Connected
[2019-04-04 13:49:31 +0000] [12] [DEBUG] ('172.18.0.1', 41930) - Connected
[2019-04-04 13:49:31 +0000] [12] [DEBUG] ('172.18.0.1', 41932) - Connected
[2019-04-04 13:49:31 +0000] [12] [DEBUG] ('172.18.0.1', 41934) - Connected
[2019-04-04 13:49:31 +0000] [12] [DEBUG] ('172.18.0.1', 41938) - Connected
[2019-04-04 13:49:31 +0000] [12] [DEBUG] ('172.18.0.1', 41936) - Connected
[2019-04-04 13:49:31 +0000] [11] [DEBUG] ('172.18.0.1', 41918) - Connected
[2019-04-04 13:49:32 +0000] [11] [DEBUG] ('172.18.0.1', 41940) - Connected
[2019-04-04 13:49:32 +0000] [8] [DEBUG] ('172.18.0.1', 41944) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 41948) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 41950) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 41952) - Connected
[2019-04-04 13:49:32 +0000] [8] [DEBUG] ('172.18.0.1', 41954) - Connected
[2019-04-04 13:49:32 +0000] [12] [DEBUG] ('172.18.0.1', 41946) - Connected
[2019-04-04 13:49:32 +0000] [8] [DEBUG] ('172.18.0.1', 41942) - Connected
[2019-04-04 13:49:32 +0000] [8] [DEBUG] ('172.18.0.1', 41956) - Connected
[2019-04-04 13:49:32 +0000] [8] [DEBUG] ('172.18.0.1', 41958) - Connected
[2019-04-04 13:49:32 +0000] [8] [DEBUG] ('172.18.0.1', 41960) - Connected
[2019-04-04 13:49:32 +0000] [8] [DEBUG] ('172.18.0.1', 41962) - Connected
[2019-04-04 13:49:32 +0000] [8] [DEBUG] ('172.18.0.1', 41964) - Connected
[2019-04-04 13:49:32 +0000] [8] [DEBUG] ('172.18.0.1', 41966) - Connected
[2019-04-04 13:49:32 +0000] [8] [DEBUG] ('172.18.0.1', 41968) - Connected
[2019-04-04 13:49:32 +0000] [8] [DEBUG] ('172.18.0.1', 41972) - Connected
[2019-04-04 13:49:32 +0000] [8] [DEBUG] ('172.18.0.1', 41970) - Connected
[2019-04-04 13:49:32 +0000] [8] [DEBUG] ('172.18.0.1', 41974) - Connected
[2019-04-04 13:49:32 +0000] [8] [DEBUG] ('172.18.0.1', 41976) - Connected
[2019-04-04 13:49:32 +0000] [8] [DEBUG] ('172.18.0.1', 41978) - Connected
[2019-04-04 13:49:32 +0000] [8] [DEBUG] ('172.18.0.1', 41980) - Connected
[2019-04-04 13:49:32 +0000] [8] [DEBUG] ('172.18.0.1', 41982) - Connected
[2019-04-04 13:49:32 +0000] [8] [DEBUG] ('172.18.0.1', 41984) - Connected
[2019-04-04 13:49:32 +0000] [8] [DEBUG] ('172.18.0.1', 41986) - Connected
[2019-04-04 13:49:32 +0000] [8] [DEBUG] ('172.18.0.1', 41988) - Connected
[2019-04-04 13:49:32 +0000] [12] [DEBUG] ('172.18.0.1', 42028) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 41990) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 41992) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 41994) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 41996) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 41998) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 42000) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 42002) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 42004) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 42006) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 42008) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 42010) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 42012) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 42014) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 42016) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 42018) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 42020) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 42022) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 42024) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 42026) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 42030) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 42032) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 42036) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 42034) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 42038) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 42040) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 42042) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 42044) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 42048) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 42050) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 42052) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 42054) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 42056) - Connected
[2019-04-04 13:49:32 +0000] [8] [DEBUG] ('172.18.0.1', 42058) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 42062) - Connected
[2019-04-04 13:49:32 +0000] [8] [DEBUG] ('172.18.0.1', 42060) - Connected
[2019-04-04 13:49:32 +0000] [11] [DEBUG] ('172.18.0.1', 42046) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 42064) - Connected
[2019-04-04 13:49:32 +0000] [11] [DEBUG] ('172.18.0.1', 42066) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 42068) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 42070) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 42072) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 42074) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 42076) - Connected
[2019-04-04 13:49:32 +0000] [11] [DEBUG] ('172.18.0.1', 42078) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 42082) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 42084) - Connected
[2019-04-04 13:49:32 +0000] [11] [DEBUG] ('172.18.0.1', 42080) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 42088) - Connected
[2019-04-04 13:49:32 +0000] [12] [DEBUG] ('172.18.0.1', 42086) - Connected
[2019-04-04 13:49:32 +0000] [8] [DEBUG] ('172.18.0.1', 42090) - Connected
[2019-04-04 13:49:32 +0000] [8] [DEBUG] ('172.18.0.1', 42094) - Connected
[2019-04-04 13:49:32 +0000] [12] [DEBUG] ('172.18.0.1', 42092) - Connected
[2019-04-04 13:49:32 +0000] [8] [DEBUG] ('172.18.0.1', 42096) - Connected
[2019-04-04 13:49:32 +0000] [8] [DEBUG] ('172.18.0.1', 42098) - Connected
[2019-04-04 13:49:32 +0000] [8] [DEBUG] ('172.18.0.1', 42100) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 42102) - Connected
[2019-04-04 13:49:32 +0000] [9] [DEBUG] ('172.18.0.1', 42104) - Connected
[2019-04-04 13:49:32 +0000] [8] [DEBUG] ('172.18.0.1', 42106) - Connected
[2019-04-04 13:49:32 +0000] [8] [DEBUG] ('172.18.0.1', 42108) - Connected
[2019-04-04 13:49:33 +0000] [9] [DEBUG] ('172.18.0.1', 42118) - Connected
[2019-04-04 13:49:33 +0000] [9] [DEBUG] ('172.18.0.1', 42120) - Connected
[2019-04-04 13:49:33 +0000] [9] [DEBUG] ('172.18.0.1', 42122) - Connected
[2019-04-04 13:49:33 +0000] [9] [DEBUG] ('172.18.0.1', 42124) - Connected
[2019-04-04 13:49:32 +0000] [8] [DEBUG] ('172.18.0.1', 42110) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42112) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42114) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42116) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42126) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42128) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42130) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42132) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42134) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42136) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42138) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42140) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42142) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42144) - Connected
[2019-04-04 13:49:33 +0000] [12] [DEBUG] ('172.18.0.1', 42146) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42148) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42150) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42152) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42154) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42156) - Connected
[2019-04-04 13:49:33 +0000] [9] [DEBUG] ('172.18.0.1', 42158) - Connected
[2019-04-04 13:49:33 +0000] [11] [DEBUG] ('172.18.0.1', 42160) - Connected
[2019-04-04 13:49:33 +0000] [11] [DEBUG] ('172.18.0.1', 42164) - Connected
[2019-04-04 13:49:33 +0000] [9] [DEBUG] ('172.18.0.1', 42166) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42168) - Connected
[2019-04-04 13:49:33 +0000] [9] [DEBUG] ('172.18.0.1', 42170) - Connected
[2019-04-04 13:49:33 +0000] [9] [DEBUG] ('172.18.0.1', 42172) - Connected
[2019-04-04 13:49:33 +0000] [9] [DEBUG] ('172.18.0.1', 42174) - Connected
[2019-04-04 13:49:33 +0000] [9] [DEBUG] ('172.18.0.1', 42178) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42180) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42182) - Connected
[2019-04-04 13:49:33 +0000] [11] [DEBUG] ('172.18.0.1', 42176) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42184) - Connected
[2019-04-04 13:49:33 +0000] [12] [DEBUG] ('172.18.0.1', 42186) - Connected
[2019-04-04 13:49:33 +0000] [12] [DEBUG] ('172.18.0.1', 42188) - Connected
[2019-04-04 13:49:33 +0000] [9] [DEBUG] ('172.18.0.1', 42190) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42194) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42196) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42198) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42200) - Connected
[2019-04-04 13:49:33 +0000] [9] [DEBUG] ('172.18.0.1', 42192) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42202) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42204) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42206) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42208) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42210) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42212) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42214) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42216) - Connected
[2019-04-04 13:49:33 +0000] [9] [DEBUG] ('172.18.0.1', 42220) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42218) - Connected
[2019-04-04 13:49:33 +0000] [9] [DEBUG] ('172.18.0.1', 42222) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42230) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42232) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42240) - Connected
[2019-04-04 13:49:33 +0000] [9] [DEBUG] ('172.18.0.1', 42234) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42244) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42246) - Connected
[2019-04-04 13:49:33 +0000] [9] [DEBUG] ('172.18.0.1', 42236) - Connected
[2019-04-04 13:49:33 +0000] [9] [DEBUG] ('172.18.0.1', 42238) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42248) - Connected
[2019-04-04 13:49:33 +0000] [9] [DEBUG] ('172.18.0.1', 42242) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42250) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42254) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42252) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42256) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42258) - Connected
[2019-04-04 13:49:33 +0000] [8] [DEBUG] ('172.18.0.1', 42262) - Connected
[2019-04-04 13:49:33 +0000] [9] [DEBUG] ('172.18.0.1', 42264) - Connected
[2019-04-04 13:49:33 +0000] [9] [DEBUG] ('172.18.0.1', 42266) - Connected
[2019-04-04 13:49:33 +0000] [12] [DEBUG] ('172.18.0.1', 42228) - Connected
[2019-04-04 13:49:33 +0000] [12] [DEBUG] ('172.18.0.1', 42260) - Connected
[2019-04-04 13:49:34 +0000] [12] [INFO] ('172.18.0.1', 41828) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:34 +0000] [11] [INFO] ('172.18.0.1', 41826) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:34 +0000] [11] [DEBUG] ('172.18.0.1', 41826) - Disconnected
[2019-04-04 13:49:34 +0000] [12] [DEBUG] ('172.18.0.1', 41828) - Disconnected
[2019-04-04 13:49:34 +0000] [11] [INFO] ('172.18.0.1', 41830) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:34 +0000] [11] [DEBUG] ('172.18.0.1', 41830) - Disconnected
[2019-04-04 13:49:39 +0000] [11] [INFO] ('172.18.0.1', 41874) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:39 +0000] [11] [INFO] ('172.18.0.1', 41888) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:39 +0000] [11] [INFO] ('172.18.0.1', 41892) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:39 +0000] [11] [INFO] ('172.18.0.1', 41884) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:39 +0000] [11] [INFO] ('172.18.0.1', 41886) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:39 +0000] [11] [INFO] ('172.18.0.1', 41918) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:39 +0000] [11] [DEBUG] ('172.18.0.1', 41918) - Disconnected
[2019-04-04 13:49:39 +0000] [11] [DEBUG] ('172.18.0.1', 41874) - Disconnected
[2019-04-04 13:49:39 +0000] [11] [DEBUG] ('172.18.0.1', 41892) - Disconnected
[2019-04-04 13:49:40 +0000] [11] [INFO] ('172.18.0.1', 41898) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:40 +0000] [11] [INFO] ('172.18.0.1', 41894) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:40 +0000] [11] [INFO] ('172.18.0.1', 41900) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:40 +0000] [11] [DEBUG] ('172.18.0.1', 41886) - Disconnected
[2019-04-04 13:49:40 +0000] [11] [DEBUG] ('172.18.0.1', 41888) - Disconnected
[2019-04-04 13:49:40 +0000] [11] [DEBUG] ('172.18.0.1', 41884) - Disconnected
[2019-04-04 13:49:40 +0000] [11] [INFO] ('172.18.0.1', 42046) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:40 +0000] [12] [INFO] ('172.18.0.1', 41882) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:40 +0000] [12] [INFO] ('172.18.0.1', 41922) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:40 +0000] [12] [INFO] ('172.18.0.1', 41926) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:40 +0000] [11] [INFO] ('172.18.0.1', 41940) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:40 +0000] [12] [INFO] ('172.18.0.1', 42028) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:40 +0000] [11] [INFO] ('172.18.0.1', 42066) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:40 +0000] [11] [INFO] ('172.18.0.1', 41896) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:40 +0000] [11] [DEBUG] ('172.18.0.1', 41894) - Disconnected
[2019-04-04 13:49:40 +0000] [11] [DEBUG] ('172.18.0.1', 41898) - Disconnected
[2019-04-04 13:49:40 +0000] [11] [DEBUG] ('172.18.0.1', 41900) - Disconnected
[2019-04-04 13:49:40 +0000] [11] [DEBUG] ('172.18.0.1', 41940) - Disconnected
[2019-04-04 13:49:40 +0000] [11] [DEBUG] ('172.18.0.1', 42046) - Disconnected
[2019-04-04 13:49:40 +0000] [11] [DEBUG] ('172.18.0.1', 41896) - Disconnected
[2019-04-04 13:49:40 +0000] [11] [DEBUG] ('172.18.0.1', 42066) - Disconnected
[2019-04-04 13:49:40 +0000] [11] [INFO] ('172.18.0.1', 42078) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:40 +0000] [12] [INFO] ('172.18.0.1', 41930) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:40 +0000] [12] [INFO] ('172.18.0.1', 41914) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:40 +0000] [12] [INFO] ('172.18.0.1', 41934) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:40 +0000] [12] [INFO] ('172.18.0.1', 41910) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:40 +0000] [11] [DEBUG] ('172.18.0.1', 42078) - Disconnected
[2019-04-04 13:49:40 +0000] [11] [INFO] ('172.18.0.1', 42080) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:40 +0000] [11] [DEBUG] ('172.18.0.1', 42080) - Disconnected
[2019-04-04 13:49:40 +0000] [12] [INFO] ('172.18.0.1', 41938) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:40 +0000] [12] [INFO] ('172.18.0.1', 41916) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:41 +0000] [11] [INFO] ('172.18.0.1', 42160) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:41 +0000] [11] [DEBUG] ('172.18.0.1', 42160) - Disconnected
[2019-04-04 13:49:41 +0000] [12] [INFO] ('172.18.0.1', 41920) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:41 +0000] [12] [INFO] ('172.18.0.1', 41924) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:41 +0000] [12] [DEBUG] ('172.18.0.1', 41926) - Disconnected
[2019-04-04 13:49:41 +0000] [12] [DEBUG] ('172.18.0.1', 41930) - Disconnected
[2019-04-04 13:49:41 +0000] [12] [DEBUG] ('172.18.0.1', 41922) - Disconnected
[2019-04-04 13:49:41 +0000] [12] [DEBUG] ('172.18.0.1', 42028) - Disconnected
[2019-04-04 13:49:41 +0000] [12] [DEBUG] ('172.18.0.1', 41910) - Disconnected
[2019-04-04 13:49:41 +0000] [12] [DEBUG] ('172.18.0.1', 41934) - Disconnected
[2019-04-04 13:49:41 +0000] [12] [DEBUG] ('172.18.0.1', 41882) - Disconnected
[2019-04-04 13:49:41 +0000] [12] [DEBUG] ('172.18.0.1', 41914) - Disconnected
[2019-04-04 13:49:41 +0000] [12] [DEBUG] ('172.18.0.1', 41938) - Disconnected
[2019-04-04 13:49:41 +0000] [12] [DEBUG] ('172.18.0.1', 41916) - Disconnected
[2019-04-04 13:49:41 +0000] [11] [INFO] ('172.18.0.1', 42176) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:41 +0000] [11] [DEBUG] ('172.18.0.1', 42176) - Disconnected
[2019-04-04 13:49:41 +0000] [11] [INFO] ('172.18.0.1', 42164) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:41 +0000] [11] [DEBUG] ('172.18.0.1', 42164) - Disconnected
[2019-04-04 13:49:41 +0000] [12] [DEBUG] ('172.18.0.1', 41920) - Disconnected
[2019-04-04 13:49:41 +0000] [12] [DEBUG] ('172.18.0.1', 41924) - Disconnected
[2019-04-04 13:49:41 +0000] [12] [INFO] ('172.18.0.1', 41902) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:41 +0000] [12] [DEBUG] ('172.18.0.1', 41902) - Disconnected
[2019-04-04 13:49:41 +0000] [12] [INFO] ('172.18.0.1', 41928) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:41 +0000] [12] [DEBUG] ('172.18.0.1', 41928) - Disconnected
[2019-04-04 13:49:42 +0000] [12] [INFO] ('172.18.0.1', 42146) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:42 +0000] [12] [DEBUG] ('172.18.0.1', 42146) - Disconnected
[2019-04-04 13:49:42 +0000] [12] [INFO] ('172.18.0.1', 41932) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:42 +0000] [12] [DEBUG] ('172.18.0.1', 41932) - Disconnected
[2019-04-04 13:49:42 +0000] [12] [INFO] ('172.18.0.1', 42086) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:42 +0000] [12] [INFO] ('172.18.0.1', 41946) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:42 +0000] [12] [DEBUG] ('172.18.0.1', 42086) - Disconnected
[2019-04-04 13:49:42 +0000] [12] [DEBUG] ('172.18.0.1', 41946) - Disconnected
[2019-04-04 13:49:42 +0000] [12] [INFO] ('172.18.0.1', 41936) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:42 +0000] [12] [INFO] ('172.18.0.1', 42228) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:42 +0000] [12] [DEBUG] ('172.18.0.1', 42228) - Disconnected
[2019-04-04 13:49:42 +0000] [12] [DEBUG] ('172.18.0.1', 41936) - Disconnected
[2019-04-04 13:49:43 +0000] [12] [INFO] ('172.18.0.1', 42188) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:43 +0000] [12] [DEBUG] ('172.18.0.1', 42188) - Disconnected
[2019-04-04 13:49:43 +0000] [12] [INFO] ('172.18.0.1', 42186) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:43 +0000] [12] [DEBUG] ('172.18.0.1', 42186) - Disconnected
[2019-04-04 13:49:43 +0000] [12] [INFO] ('172.18.0.1', 42092) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:43 +0000] [12] [DEBUG] ('172.18.0.1', 42092) - Disconnected
[2019-04-04 13:49:43 +0000] [12] [INFO] ('172.18.0.1', 42260) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:43 +0000] [12] [DEBUG] ('172.18.0.1', 42260) - Disconnected
[2019-04-04 13:49:50 +0000] [8] [INFO] ('172.18.0.1', 41846) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:50 +0000] [8] [INFO] ('172.18.0.1', 41878) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:50 +0000] [8] [INFO] ('172.18.0.1', 41960) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:50 +0000] [8] [INFO] ('172.18.0.1', 42098) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:50 +0000] [8] [INFO] ('172.18.0.1', 41876) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:50 +0000] [8] [INFO] ('172.18.0.1', 41962) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:50 +0000] [8] [INFO] ('172.18.0.1', 42096) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:50 +0000] [8] [INFO] ('172.18.0.1', 42094) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:50 +0000] [8] [INFO] ('172.18.0.1', 42194) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:50 +0000] [8] [INFO] ('172.18.0.1', 41880) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:51 +0000] [8] [INFO] ('172.18.0.1', 42200) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:51 +0000] [8] [INFO] ('172.18.0.1', 42196) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:51 +0000] [8] [INFO] ('172.18.0.1', 42198) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:51 +0000] [8] [INFO] ('172.18.0.1', 41964) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:51 +0000] [8] [INFO] ('172.18.0.1', 42210) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:51 +0000] [8] [INFO] ('172.18.0.1', 42202) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:51 +0000] [8] [INFO] ('172.18.0.1', 42250) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:51 +0000] [8] [INFO] ('172.18.0.1', 42212) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:51 +0000] [8] [INFO] ('172.18.0.1', 42218) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:51 +0000] [8] [INFO] ('172.18.0.1', 42246) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:51 +0000] [8] [INFO] ('172.18.0.1', 42216) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:51 +0000] [8] [INFO] ('172.18.0.1', 42214) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:51 +0000] [8] [INFO] ('172.18.0.1', 42204) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:51 +0000] [8] [INFO] ('172.18.0.1', 42206) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:51 +0000] [8] [INFO] ('172.18.0.1', 42252) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:51 +0000] [8] [INFO] ('172.18.0.1', 42230) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:51 +0000] [8] [INFO] ('172.18.0.1', 42112) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:51 +0000] [8] [INFO] ('172.18.0.1', 42248) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:52 +0000] [8] [INFO] ('172.18.0.1', 42244) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:52 +0000] [9] [INFO] ('172.18.0.1', 41832) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:52 +0000] [8] [INFO] ('172.18.0.1', 42108) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:52 +0000] [8] [INFO] ('172.18.0.1', 42110) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:52 +0000] [8] [INFO] ('172.18.0.1', 42058) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:52 +0000] [8] [INFO] ('172.18.0.1', 42116) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:52 +0000] [8] [INFO] ('172.18.0.1', 42208) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:52 +0000] [8] [INFO] ('172.18.0.1', 42106) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:52 +0000] [8] [INFO] ('172.18.0.1', 41956) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:52 +0000] [8] [INFO] ('172.18.0.1', 42060) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:52 +0000] [9] [INFO] ('172.18.0.1', 41834) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:52 +0000] [9] [INFO] ('172.18.0.1', 41842) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:53 +0000] [8] [INFO] ('172.18.0.1', 42232) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:53 +0000] [8] [INFO] ('172.18.0.1', 41958) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:53 +0000] [8] [INFO] ('172.18.0.1', 41968) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:53 +0000] [8] [INFO] ('172.18.0.1', 41942) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:53 +0000] [8] [INFO] ('172.18.0.1', 42114) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:53 +0000] [8] [INFO] ('172.18.0.1', 41966) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:53 +0000] [8] [INFO] ('172.18.0.1', 42134) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:53 +0000] [9] [INFO] ('172.18.0.1', 41838) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:53 +0000] [8] [INFO] ('172.18.0.1', 41944) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:53 +0000] [9] [INFO] ('172.18.0.1', 41836) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:53 +0000] [9] [INFO] ('172.18.0.1', 41844) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:53 +0000] [9] [INFO] ('172.18.0.1', 41856) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:53 +0000] [9] [INFO] ('172.18.0.1', 41854) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:53 +0000] [9] [INFO] ('172.18.0.1', 41840) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:53 +0000] [9] [INFO] ('172.18.0.1', 41860) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:53 +0000] [9] [INFO] ('172.18.0.1', 41862) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:53 +0000] [9] [INFO] ('172.18.0.1', 41866) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:53 +0000] [9] [INFO] ('172.18.0.1', 41858) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:53 +0000] [9] [INFO] ('172.18.0.1', 41852) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:54 +0000] [9] [INFO] ('172.18.0.1', 41868) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:54 +0000] [8] [INFO] ('172.18.0.1', 42130) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:54 +0000] [8] [INFO] ('172.18.0.1', 42132) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:54 +0000] [8] [INFO] ('172.18.0.1', 42136) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:54 +0000] [8] [DEBUG] ('172.18.0.1', 42208) - Disconnected
[2019-04-04 13:49:54 +0000] [8] [DEBUG] ('172.18.0.1', 42198) - Disconnected
[2019-04-04 13:49:54 +0000] [8] [DEBUG] ('172.18.0.1', 42096) - Disconnected
[2019-04-04 13:49:54 +0000] [8] [DEBUG] ('172.18.0.1', 42218) - Disconnected
[2019-04-04 13:49:54 +0000] [8] [DEBUG] ('172.18.0.1', 42200) - Disconnected
[2019-04-04 13:49:54 +0000] [8] [DEBUG] ('172.18.0.1', 42230) - Disconnected
[2019-04-04 13:49:54 +0000] [8] [DEBUG] ('172.18.0.1', 42210) - Disconnected
[2019-04-04 13:49:54 +0000] [8] [DEBUG] ('172.18.0.1', 42206) - Disconnected
[2019-04-04 13:49:54 +0000] [8] [DEBUG] ('172.18.0.1', 41880) - Disconnected
[2019-04-04 13:49:54 +0000] [8] [DEBUG] ('172.18.0.1', 42250) - Disconnected
[2019-04-04 13:49:54 +0000] [8] [DEBUG] ('172.18.0.1', 42110) - Disconnected
[2019-04-04 13:49:54 +0000] [8] [DEBUG] ('172.18.0.1', 41876) - Disconnected
[2019-04-04 13:49:54 +0000] [8] [DEBUG] ('172.18.0.1', 42094) - Disconnected
[2019-04-04 13:49:54 +0000] [8] [DEBUG] ('172.18.0.1', 42202) - Disconnected
[2019-04-04 13:49:54 +0000] [8] [DEBUG] ('172.18.0.1', 42216) - Disconnected
[2019-04-04 13:49:54 +0000] [8] [DEBUG] ('172.18.0.1', 41962) - Disconnected
[2019-04-04 13:49:54 +0000] [8] [DEBUG] ('172.18.0.1', 41878) - Disconnected
[2019-04-04 13:49:54 +0000] [8] [DEBUG] ('172.18.0.1', 42116) - Disconnected
[2019-04-04 13:49:54 +0000] [8] [DEBUG] ('172.18.0.1', 42194) - Disconnected
[2019-04-04 13:49:54 +0000] [8] [DEBUG] ('172.18.0.1', 42058) - Disconnected
[2019-04-04 13:49:54 +0000] [8] [DEBUG] ('172.18.0.1', 42204) - Disconnected
[2019-04-04 13:49:54 +0000] [8] [DEBUG] ('172.18.0.1', 42246) - Disconnected
[2019-04-04 13:49:54 +0000] [8] [DEBUG] ('172.18.0.1', 42248) - Disconnected
[2019-04-04 13:49:54 +0000] [8] [DEBUG] ('172.18.0.1', 42212) - Disconnected
[2019-04-04 13:49:54 +0000] [8] [DEBUG] ('172.18.0.1', 41960) - Disconnected
[2019-04-04 13:49:54 +0000] [8] [DEBUG] ('172.18.0.1', 42196) - Disconnected
[2019-04-04 13:49:54 +0000] [8] [DEBUG] ('172.18.0.1', 42252) - Disconnected
[2019-04-04 13:49:54 +0000] [8] [DEBUG] ('172.18.0.1', 42112) - Disconnected
[2019-04-04 13:49:54 +0000] [8] [DEBUG] ('172.18.0.1', 42214) - Disconnected
[2019-04-04 13:49:54 +0000] [8] [DEBUG] ('172.18.0.1', 42098) - Disconnected
[2019-04-04 13:49:54 +0000] [8] [DEBUG] ('172.18.0.1', 41846) - Disconnected
[2019-04-04 13:49:54 +0000] [8] [DEBUG] ('172.18.0.1', 42244) - Disconnected
[2019-04-04 13:49:55 +0000] [8] [DEBUG] ('172.18.0.1', 41964) - Disconnected
[2019-04-04 13:49:55 +0000] [8] [DEBUG] ('172.18.0.1', 42108) - Disconnected
[2019-04-04 13:49:55 +0000] [9] [INFO] ('172.18.0.1', 41872) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:55 +0000] [9] [INFO] ('172.18.0.1', 41848) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:55 +0000] [9] [INFO] ('172.18.0.1', 42034) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:55 +0000] [9] [INFO] ('172.18.0.1', 41864) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:55 +0000] [9] [INFO] ('172.18.0.1', 42038) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:55 +0000] [8] [INFO] ('172.18.0.1', 42128) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:55 +0000] [8] [INFO] ('172.18.0.1', 42138) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:55 +0000] [9] [INFO] ('172.18.0.1', 42042) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:55 +0000] [9] [INFO] ('172.18.0.1', 42044) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:55 +0000] [9] [INFO] ('172.18.0.1', 42032) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:55 +0000] [9] [INFO] ('172.18.0.1', 42040) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:55 +0000] [9] [INFO] ('172.18.0.1', 41908) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:55 +0000] [8] [INFO] ('172.18.0.1', 42144) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:55 +0000] [8] [INFO] ('172.18.0.1', 42156) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:56 +0000] [8] [INFO] ('172.18.0.1', 41972) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:56 +0000] [8] [INFO] ('172.18.0.1', 42140) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:56 +0000] [8] [INFO] ('172.18.0.1', 41954) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:56 +0000] [8] [DEBUG] ('172.18.0.1', 41956) - Disconnected
[2019-04-04 13:49:56 +0000] [8] [DEBUG] ('172.18.0.1', 42060) - Disconnected
[2019-04-04 13:49:56 +0000] [8] [DEBUG] ('172.18.0.1', 42106) - Disconnected
[2019-04-04 13:49:56 +0000] [9] [INFO] ('172.18.0.1', 42024) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:56 +0000] [9] [INFO] ('172.18.0.1', 42020) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:56 +0000] [9] [INFO] ('172.18.0.1', 41904) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:56 +0000] [8] [INFO] ('172.18.0.1', 42142) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:56 +0000] [8] [INFO] ('172.18.0.1', 41984) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:56 +0000] [8] [INFO] ('172.18.0.1', 41976) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:56 +0000] [9] [INFO] ('172.18.0.1', 42104) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:56 +0000] [8] [INFO] ('172.18.0.1', 42182) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:56 +0000] [8] [INFO] ('172.18.0.1', 41978) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:56 +0000] [9] [INFO] ('172.18.0.1', 42036) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:56 +0000] [9] [INFO] ('172.18.0.1', 42022) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:56 +0000] [8] [INFO] ('172.18.0.1', 41980) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:56 +0000] [8] [INFO] ('172.18.0.1', 42126) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:56 +0000] [9] [INFO] ('172.18.0.1', 42030) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:56 +0000] [8] [INFO] ('172.18.0.1', 41974) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:56 +0000] [9] [INFO] ('172.18.0.1', 41850) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:56 +0000] [8] [DEBUG] ('172.18.0.1', 41942) - Disconnected
[2019-04-04 13:49:56 +0000] [8] [DEBUG] ('172.18.0.1', 41966) - Disconnected
[2019-04-04 13:49:56 +0000] [9] [INFO] ('172.18.0.1', 41906) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:56 +0000] [9] [INFO] ('172.18.0.1', 42052) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:56 +0000] [9] [INFO] ('172.18.0.1', 42048) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:56 +0000] [8] [DEBUG] ('172.18.0.1', 41958) - Disconnected
[2019-04-04 13:49:56 +0000] [8] [DEBUG] ('172.18.0.1', 42136) - Disconnected
[2019-04-04 13:49:56 +0000] [8] [DEBUG] ('172.18.0.1', 41968) - Disconnected
[2019-04-04 13:49:56 +0000] [8] [DEBUG] ('172.18.0.1', 42232) - Disconnected
[2019-04-04 13:49:56 +0000] [8] [DEBUG] ('172.18.0.1', 42130) - Disconnected
[2019-04-04 13:49:56 +0000] [9] [INFO] ('172.18.0.1', 41870) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:56 +0000] [9] [INFO] ('172.18.0.1', 42062) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:56 +0000] [9] [INFO] ('172.18.0.1', 42070) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:56 +0000] [9] [INFO] ('172.18.0.1', 42120) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:56 +0000] [9] [INFO] ('172.18.0.1', 42068) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:56 +0000] [9] [INFO] ('172.18.0.1', 42056) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:56 +0000] [9] [INFO] ('172.18.0.1', 42064) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:56 +0000] [9] [INFO] ('172.18.0.1', 41948) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:56 +0000] [9] [INFO] ('172.18.0.1', 42054) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:56 +0000] [8] [DEBUG] ('172.18.0.1', 42132) - Disconnected
[2019-04-04 13:49:56 +0000] [8] [DEBUG] ('172.18.0.1', 42114) - Disconnected
[2019-04-04 13:49:56 +0000] [8] [DEBUG] ('172.18.0.1', 41944) - Disconnected
[2019-04-04 13:49:56 +0000] [8] [DEBUG] ('172.18.0.1', 42134) - Disconnected
[2019-04-04 13:49:56 +0000] [8] [INFO] ('172.18.0.1', 41970) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:56 +0000] [8] [INFO] ('172.18.0.1', 42154) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:56 +0000] [9] [INFO] ('172.18.0.1', 42076) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:56 +0000] [9] [INFO] ('172.18.0.1', 42026) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:56 +0000] [9] [INFO] ('172.18.0.1', 42074) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:56 +0000] [9] [INFO] ('172.18.0.1', 42050) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:56 +0000] [9] [INFO] ('172.18.0.1', 42118) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:57 +0000] [8] [INFO] ('172.18.0.1', 42150) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:57 +0000] [8] [DEBUG] ('172.18.0.1', 42156) - Disconnected
[2019-04-04 13:49:57 +0000] [9] [INFO] ('172.18.0.1', 41950) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:57 +0000] [8] [DEBUG] ('172.18.0.1', 41972) - Disconnected
[2019-04-04 13:49:57 +0000] [8] [DEBUG] ('172.18.0.1', 42128) - Disconnected
[2019-04-04 13:49:57 +0000] [8] [DEBUG] ('172.18.0.1', 42140) - Disconnected
[2019-04-04 13:49:57 +0000] [8] [DEBUG] ('172.18.0.1', 41954) - Disconnected
[2019-04-04 13:49:57 +0000] [8] [DEBUG] ('172.18.0.1', 42138) - Disconnected
[2019-04-04 13:49:57 +0000] [8] [DEBUG] ('172.18.0.1', 42144) - Disconnected
[2019-04-04 13:49:57 +0000] [8] [INFO] ('172.18.0.1', 42152) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:57 +0000] [8] [INFO] ('172.18.0.1', 41988) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:57 +0000] [8] [INFO] ('172.18.0.1', 42148) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:57 +0000] [9] [INFO] ('172.18.0.1', 42124) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:57 +0000] [8] [INFO] ('172.18.0.1', 42180) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:57 +0000] [8] [INFO] ('172.18.0.1', 42184) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:57 +0000] [8] [INFO] ('172.18.0.1', 41986) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:57 +0000] [9] [INFO] ('172.18.0.1', 41912) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:57 +0000] [8] [DEBUG] ('172.18.0.1', 41978) - Disconnected
[2019-04-04 13:49:57 +0000] [9] [INFO] ('172.18.0.1', 42072) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:57 +0000] [9] [INFO] ('172.18.0.1', 41952) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:57 +0000] [8] [DEBUG] ('172.18.0.1', 42126) - Disconnected
[2019-04-04 13:49:57 +0000] [8] [DEBUG] ('172.18.0.1', 41976) - Disconnected
[2019-04-04 13:49:57 +0000] [8] [DEBUG] ('172.18.0.1', 42182) - Disconnected
[2019-04-04 13:49:57 +0000] [8] [DEBUG] ('172.18.0.1', 41974) - Disconnected
[2019-04-04 13:49:57 +0000] [8] [DEBUG] ('172.18.0.1', 41980) - Disconnected
[2019-04-04 13:49:57 +0000] [8] [DEBUG] ('172.18.0.1', 41984) - Disconnected
[2019-04-04 13:49:57 +0000] [8] [DEBUG] ('172.18.0.1', 42142) - Disconnected
[2019-04-04 13:49:57 +0000] [8] [INFO] ('172.18.0.1', 41982) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:57 +0000] [8] [INFO] ('172.18.0.1', 42168) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:57 +0000] [8] [INFO] ('172.18.0.1', 42090) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:57 +0000] [8] [INFO] ('172.18.0.1', 42258) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:57 +0000] [8] [INFO] ('172.18.0.1', 42262) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:57 +0000] [8] [DEBUG] ('172.18.0.1', 41970) - Disconnected
[2019-04-04 13:49:57 +0000] [8] [DEBUG] ('172.18.0.1', 42150) - Disconnected
[2019-04-04 13:49:57 +0000] [8] [DEBUG] ('172.18.0.1', 42154) - Disconnected
[2019-04-04 13:49:57 +0000] [8] [INFO] ('172.18.0.1', 42240) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:57 +0000] [8] [INFO] ('172.18.0.1', 42254) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:57 +0000] [8] [INFO] ('172.18.0.1', 42100) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:57 +0000] [8] [DEBUG] ('172.18.0.1', 42180) - Disconnected
[2019-04-04 13:49:57 +0000] [8] [DEBUG] ('172.18.0.1', 42184) - Disconnected
[2019-04-04 13:49:57 +0000] [8] [DEBUG] ('172.18.0.1', 42148) - Disconnected
[2019-04-04 13:49:57 +0000] [8] [DEBUG] ('172.18.0.1', 41986) - Disconnected
[2019-04-04 13:49:57 +0000] [8] [DEBUG] ('172.18.0.1', 41988) - Disconnected
[2019-04-04 13:49:57 +0000] [8] [DEBUG] ('172.18.0.1', 42152) - Disconnected
[2019-04-04 13:49:57 +0000] [8] [INFO] ('172.18.0.1', 42256) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:57 +0000] [8] [DEBUG] ('172.18.0.1', 42090) - Disconnected
[2019-04-04 13:49:57 +0000] [8] [DEBUG] ('172.18.0.1', 42258) - Disconnected
[2019-04-04 13:49:57 +0000] [8] [DEBUG] ('172.18.0.1', 41982) - Disconnected
[2019-04-04 13:49:57 +0000] [8] [DEBUG] ('172.18.0.1', 42168) - Disconnected
[2019-04-04 13:49:57 +0000] [8] [DEBUG] ('172.18.0.1', 42262) - Disconnected
[2019-04-04 13:49:57 +0000] [8] [DEBUG] ('172.18.0.1', 42254) - Disconnected
[2019-04-04 13:49:57 +0000] [8] [DEBUG] ('172.18.0.1', 42100) - Disconnected
[2019-04-04 13:49:57 +0000] [8] [DEBUG] ('172.18.0.1', 42240) - Disconnected
[2019-04-04 13:49:57 +0000] [8] [DEBUG] ('172.18.0.1', 42256) - Disconnected
[2019-04-04 13:49:57 +0000] [9] [INFO] ('172.18.0.1', 42082) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:58 +0000] [9] [INFO] ('172.18.0.1', 42174) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:58 +0000] [9] [INFO] ('172.18.0.1', 41992) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:58 +0000] [9] [INFO] ('172.18.0.1', 42122) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:58 +0000] [9] [DEBUG] ('172.18.0.1', 41862) - Disconnected
[2019-04-04 13:49:58 +0000] [9] [DEBUG] ('172.18.0.1', 41868) - Disconnected
[2019-04-04 13:49:58 +0000] [9] [DEBUG] ('172.18.0.1', 41858) - Disconnected
[2019-04-04 13:49:58 +0000] [9] [DEBUG] ('172.18.0.1', 41852) - Disconnected
[2019-04-04 13:49:58 +0000] [9] [DEBUG] ('172.18.0.1', 41842) - Disconnected
[2019-04-04 13:49:58 +0000] [9] [DEBUG] ('172.18.0.1', 41866) - Disconnected
[2019-04-04 13:49:58 +0000] [9] [DEBUG] ('172.18.0.1', 41860) - Disconnected
[2019-04-04 13:49:58 +0000] [9] [DEBUG] ('172.18.0.1', 41832) - Disconnected
[2019-04-04 13:49:58 +0000] [9] [DEBUG] ('172.18.0.1', 41838) - Disconnected
[2019-04-04 13:49:58 +0000] [9] [DEBUG] ('172.18.0.1', 41856) - Disconnected
[2019-04-04 13:49:58 +0000] [9] [DEBUG] ('172.18.0.1', 41836) - Disconnected
[2019-04-04 13:49:58 +0000] [9] [DEBUG] ('172.18.0.1', 41844) - Disconnected
[2019-04-04 13:49:58 +0000] [9] [DEBUG] ('172.18.0.1', 41854) - Disconnected
[2019-04-04 13:49:58 +0000] [9] [DEBUG] ('172.18.0.1', 41840) - Disconnected
[2019-04-04 13:49:58 +0000] [9] [DEBUG] ('172.18.0.1', 41834) - Disconnected
[2019-04-04 13:49:59 +0000] [9] [INFO] ('172.18.0.1', 42170) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:59 +0000] [9] [INFO] ('172.18.0.1', 41998) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:59 +0000] [9] [INFO] ('172.18.0.1', 42000) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:59 +0000] [9] [INFO] ('172.18.0.1', 42084) - "POST /signals/fanout HTTP/1.1" 200
[2019-04-04 13:49:59 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:8)
[2019-04-04 13:49:59 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:9)
[2019-04-04 13:49:59 +0000] [96] [INFO] Booting worker with pid: 96
[2019-04-04 13:49:59 +0000] [1] [DEBUG] 3 workers
[2019-04-04 13:49:59 +0000] [97] [INFO] Booting worker with pid: 97
[2019-04-04 13:49:59 +0000] [1] [DEBUG] 4 workers
WARNING:root:email-validator not installed, email fields will be treated as str.
To install, run: pip install email-validatorWARNING:root:email-validator not installed, email fields will be treated as str.
To install, run: pip install email-validator

[2019-04-04 13:50:01 +0000] [97] [INFO] Started server process [97]
[2019-04-04 13:50:01 +0000] [96] [INFO] Started server process [96]
[2019-04-04 13:50:01 +0000] [96] [INFO] Waiting for application startup.
[2019-04-04 13:50:01 +0000] [97] [INFO] Waiting for application startup.

opened by israelpasos 15

Docker images out of date

Hello,

the docker CI build is not triggered anymore and the images in the hub are out of date.

Would be great if they can be updated again @tiangolo

Thanks!
answered

opened by jenswet 9
how to develop ?

Hi,

I like to develop within the docker container so that I use the same environment that is used later in prod.

I run: docker run -it --rm -v /c/Users/myuser/chat/api:/app -p 8090:8000 my-image-name:0.0.2 uvicorn main:app --reload

So I map using -v my local directory inside the container. When I change a file locally the reloader within docker detecs it and restarts the application. That works fine. But if I try to connect to http://localhost:8090/ I get a "The connection was reset" message in the webbrowser (firefox).

Uvicorn logs that its running on http://127.0.0.1:8000 so -p 8090:8000 should work - I thought :)

my-image-name:0.0.2 is based on tiangolo/uvicorn-gunicorn-fastapi:python3.8-slim and basically only installs some python packages and then does a COPY /api /app I develop on Windows 10 using WSL (not WSL2).

Does anyone else had this issue ?

Thanks!
answered

opened by yellow-sock 9
Debug mode?

Trying to figure out how to turn on auto-reloading (e.g. debug mode) while using docker. I develop in the docker container by volume mounting the app directory into the docker container so any changes I make to the code are available immediately inside the running docker container. I can't figure out how to start debug mode using gunicorn with uvicorn.

Any ideas?

PS Great project and thanks!

opened by wshayes 8
how to debug an application

Hi Is it possible debugging an app (for example using the pycharm or vscode debugger)? The only solution I found so far is changing the log level to DEBUG but it's not enough for properly debugging an API
answered

opened by talnagar 6
The server refused to connect

I am running the image in a container. It runs successfully. The terminal output is: [2019-06-18 15:17:00 +0000] [1] [INFO] Starting gunicorn 19.9.0 [2019-06-18 15:17:00 +0000] [1] [INFO] Listening at: http://0.0.0.0:80 (1) [2019-06-18 15:17:00 +0000] [1] [INFO] Using worker: uvicorn.workers.UvicornWorker [2019-06-18 15:17:00 +0000] [8] [INFO] Booting worker with pid: 8 [2019-06-18 15:17:00 +0000] [9] [INFO] Booting worker with pid: 9 [2019-06-18 15:17:01 +0000] [8] [INFO] Started server process [8] [2019-06-18 15:17:01 +0000] [9] [INFO] Started server process [9] [2019-06-18 15:17:01 +0000] [9] [INFO] Waiting for application startup. [2019-06-18 15:17:01 +0000] [8] [INFO] Waiting for application startup.

But whenever I hit 0.0.0.0:80, it says "Refused to connect". It only happens if I connect it through a docker container. If I run it without a docker container, it works like charm.

Edit: None of the ports are working. So changing port is not solving the problem.

opened by coderwassananmol 6
Could not import (fastapi.)HTTPException but starlette OK

Hi tiangolo.

Thank you for your docker images

However, with this one "FROM tiangolo/uvicorn-gunicorn-fastapi:python3.7-alpine3.8"

I had to import HTTPException from starlette because it wasn't known in fastapi, in my import.

fixed for me but I thought it would be interesting for you to know

opened by JSchoreels 6
High security findings

We're using the tiangolo/uvicorn-gunicorn-fastapi:python3.8-slim image and after a image scan we got a report with 2 high findings relating to perl.

`

featurename | featureversion | vulnerability | namespace | description | link | severity | fixedby -- | -- | -- | -- | -- | -- | -- | -- perl | 5.28.1-6 | CVE-2020-10878 | debian:10 | Perl before 5.30.3 has an integer overflow related to mishandling of a "PL_regkind[OP(n)] == NOTHING" situation. A crafted regular expression could lead to malformed bytecode with a possibility of instruction injection. | https://security-tracker.debian.org/tracker/CVE-2020-10878 | High | perl | 5.28.1-6 | CVE-2020-10543 | debian:10 | Perl before 5.30.3 on 32-bit platforms allows a heap-based buffer overflow because nested regular expression quantifiers have an integer overflow. | https://security-tracker.debian.org/tracker/CVE-2020-10543 | High |

`

is it possible to upgrade perl to 5.30.3?

opened by Arrrunan 5

Startup-loop when using for machine learning deployment

I'm trying to get this container running for our production API endpoints for fasttext ml models. When running locally with uvicorn main:app we get everything running without problems. When running in docker we get an infinite startup loop. Gunicorn is just spaning new workers without taking the time to startup completely. Loading the model takes some time for sure (it's 1.6GB).

[2019-07-01 11:14:38 +0000] [1] [INFO] Starting gunicorn 19.9.0
[2019-07-01 11:14:38 +0000] [1] [DEBUG] Arbiter booted
[2019-07-01 11:14:38 +0000] [1] [INFO] Listening at: http://0.0.0.0:80 (1)
[2019-07-01 11:14:38 +0000] [1] [INFO] Using worker: uvicorn.workers.UvicornWorker
[2019-07-01 11:14:38 +0000] [9] [INFO] Booting worker with pid: 9
[2019-07-01 11:14:38 +0000] [11] [INFO] Booting worker with pid: 11
[2019-07-01 11:14:39 +0000] [1] [DEBUG] 2 workers
email-validator not installed, email fields will be treated as str.
To install, run: pip install email-validator
email-validator not installed, email fields will be treated as str.
To install, run: pip install email-validator
Model is now loading from disk..
/usr/local/lib/python3.7/site-packages/smart_open/smart_open_lib.py:398: UserWarning: This function is deprecated, use smart_open.open instead. See the migration notes for details: https://github.com/RaRe-Technologies/smart_open/blob/master/README.rst#migrating-to-the-new-open-function
  'See the migration notes for details: %s' % _MIGRATION_NOTES_URL
Model is now loading from disk..
/usr/local/lib/python3.7/site-packages/smart_open/smart_open_lib.py:398: UserWarning: This function is deprecated, use smart_open.open instead. See the migration notes for details: https://github.com/RaRe-Technologies/smart_open/blob/master/README.rst#migrating-to-the-new-open-function
  'See the migration notes for details: %s' % _MIGRATION_NOTES_URL
[2019-07-01 11:14:48 +0000] [13] [INFO] Booting worker with pid: 13
email-validator not installed, email fields will be treated as str.
To install, run: pip install email-validator
Model is now loading from disk..
/usr/local/lib/python3.7/site-packages/smart_open/smart_open_lib.py:398: UserWarning: This function is deprecated, use smart_open.open instead. See the migration notes for details: https://github.com/RaRe-Technologies/smart_open/blob/master/README.rst#migrating-to-the-new-open-function
  'See the migration notes for details: %s' % _MIGRATION_NOTES_URL
[2019-07-01 11:14:54 +0000] [15] [INFO] Booting worker with pid: 15
email-validator not installed, email fields will be treated as str.
To install, run: pip install email-validator
Model is now loading from disk..
/usr/local/lib/python3.7/site-packages/smart_open/smart_open_lib.py:398: UserWarning: This function is deprecated, use smart_open.open instead. See the migration notes for details: https://github.com/RaRe-Technologies/smart_open/blob/master/README.rst#migrating-to-the-new-open-function
  'See the migration notes for details: %s' % _MIGRATION_NOTES_URL
^C[2019-07-01 11:15:07 +0000] [1] [INFO] Handling signal: int
[2019-07-01 11:15:07 +0000] [17] [INFO] Booting worker with pid: 17
email-validator not installed, email fields will be treated as str.
To install, run: pip install email-validator
Model is now loading from disk..

Our Dockerfile looks like this:

FROM tiangolo/uvicorn-gunicorn-fastapi:python3.7
# We expose port 80

LABEL MAINTAINER="greple.ai DEV | Jannik Zinkl <[email protected]>"

ARG MODEL_FOLDER

COPY ${MODEL_FOLDER}/requirements.txt /app

RUN pip install -r requirements.txt \ 
    && rm -rf /var/cache/apk/* \
    && rm -rf requirements.txt
COPY ${MODEL_FOLDER}/ /app

I couldn't find any timeout setting or anything related to this issue. Furthermore, I don't get errors even when using debug logging.

Any hint is highly appreciated!

opened by JannikZed 5

APScheduler logs not showing in docker

The jobs spin up fine when I run locally, but when I run through docker, each of the workers duplicates the jobs

from fastapi import FastAPI
from models.db import init_db
from routers.portfolio import router as portfolio_router
from routers.balance import router as balance_router
from routers.transaction import router as transaction_router

from idom import component, html
from idom.backend.fastapi import configure
import os
from tasks import manage_portfolio_task, fetch_liquidity_changes
from apscheduler.schedulers.asyncio import AsyncIOScheduler

from loguru import logger

# Configure Logs
from log_settings import setup_logger_from_settings, LoggingSettings

# Configure endpoints
app = FastAPI()
app.include_router(portfolio_router, prefix="/portfolio", tags=["Portfolio"])
app.include_router(balance_router, prefix="/balance", tags=["Balance"])
app.include_router(transaction_router, prefix="/transaction", tags=["Transaction"])

# Configure DB
@app.on_event("startup")
async def on_startup():
    # Startup db
    await init_db()
    # Configure Logs
    if not os.environ.get("LOG_LEVEL"):
        os.environ["LOG_LEVEL"] = "INFO"
    setup_logger_from_settings(
        LoggingSettings(
            level=os.environ.get("LOG_LEVEL"),
            filepath=os.path.join(
                os.path.dirname(os.path.abspath(__file__)),
                "config",
                "log.log",
            ),
        )
    )

    # Setup Scheduler
    scheduler = AsyncIOScheduler()
    scheduler.add_job(manage_portfolio_task, "interval", seconds=10)
    scheduler.add_job(fetch_liquidity_changes, "interval", minutes=5)
    scheduler.start()


# Configure Frontend (IDOM)
@component
def BalanceBot():
    return html.h1("Hello, world!")


configure(app, BalanceBot)


# For local dev
if __name__ == "__main__":
    import uvicorn
    uvicorn.run(app, host="0.0.0.0", port=8000)

From research I've done, the workaround around is to preload the app, however when I try to do this both from the CLI or custom guincorn_conf.py file (setting preload_app=True), I am still experiencing the duplication.

When moving the following code outside of the on_statup() function or inside theif __name__ == "__main__": block, the scheduler does not seem to start at all

    scheduler = AsyncIOScheduler()
    scheduler.add_job(manage_portfolio_task, "interval", seconds=10)
    scheduler.add_job(fetch_liquidity_changes, "interval", minutes=5)
    scheduler.start()

opened by ethanopp 1

⬆️ Bump actions/setup-python from 4.3.0 to 4.4.0
Bumps actions/setup-python from 4.3.0 to 4.4.0.

Release notes

Sourced from actions/setup-python's releases.

Add support to install multiple python versions

In scope of this release we added support to install multiple python versions. For this you can try to use this snippet:

- uses: actions/[email protected] with: python-version: | 3.8 3.9 3.10

Besides, we changed logic with throwing the error for GHES if cache is unavailable to warn (actions/setup-python#566).

Improve error handling and messages

In scope of this release we added improved error message to put operating system and its version in the logs (actions/setup-python#559). Besides, the release

fixes issue about specifying architecture for pypy-nightly on Windows with related pull request.

improves error handling for Http Errors (actions/setup-python#511).

updates minimatch (actions/setup-python#558).

Commits

5ccb29d Install multiple python versions (#567)

c3e0339 Update action to use reusable workflows (#569)

206e984 refactor: Use early return pattern to avoid nested conditions (#566)

2c3dd9e Add OS info to the error message (#559)

76bbdfa Update minimatch (#558)

1aafadc Caching projects that use setup.py (#549)

b80efd6 Update to latest actions/publish-action (#546)

5cddb27 Recommend setting python-version (#545)

47c4a7a fix(ci): run .github/workflows/workflow.yml on ubuntu-20.04 (#535)

af57b64 Extend docu regarding rate limit issues. (#510)

Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR

@dependabot recreate will recreate this PR, overwriting any edits that have been made to it

@dependabot merge will merge this PR after your CI passes on it

@dependabot squash and merge will squash and merge this PR after your CI passes on it

@dependabot cancel merge will cancel a previously requested merge and block automerging

@dependabot reopen will reopen this PR if it is closed

@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually

@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

dependencies github_actions
opened by dependabot[bot] 0
ModuleNotFoundError: No module named 'app'
Hi, the error as mentioned in the title is thrown when running the container. Below I tried to describe my setup in detail.

I have setup everything exactly as described in the readme. Therefore, this is how my Dockerfile looks like.

FROM python:3.10 as requirements-stage WORKDIR /tmp RUN pip install poetry COPY ./pyproject.toml ./poetry.lock* /tmp/ RUN poetry export -f requirements.txt --output requirements.txt --without-hashes FROM tiangolo/uvicorn-gunicorn-fastapi:python3.10 COPY --from=requirements-stage /tmp/requirements.txt /app/requirements.txt RUN pip install --no-cache-dir --upgrade -r /app/requirements.txt COPY ./app /app

my directory structure is as follows.

app ├── main.py ├── api │ └── __init__.py | └── user.py └── tests └── __init__.py pyproject.toml Dockerfile

then, in the app/main.py I am trying to import user from the api-directory by doing: from app.api import user

When running the container, the following error is thrown. ModuleNotFoundError: No module named 'app'

This is probably because app is not in the PYTHONPATH. I have tried to add it to the Dockerfile, but this did not help. I want to keep the structure and the way of importing it as is as it is also needed by my test setup.

How can I fix this? The problem has probably a very trivial solution, but I am currently stuck.

Thanks in advance
opened by jmandt 0

Upgrade from python3.8 to python3.11 fails

Hello,

just wanted to report that I have an existing Dockerfile that is build on top of FROM tiangolo/uvicorn-gunicorn-fastapi:python3.8-2022-11-25 Everything works great!

When I try to upgrade the Python version to 3.11 I receive the following error, when installing my dependencies.

> [build-stage 5/5] RUN pip install --no-cache-dir -q -r requirements.txt:
#9 5.388   error: subprocess-exited-with-error
#9 5.388
#9 5.388   × Preparing metadata (pyproject.toml) did not run successfully.
#9 5.388   │ exit code: 1
#9 5.388   ╰─> [6 lines of output]
#9 5.388
#9 5.388       Cargo, the Rust package manager, is not installed or is not on PATH.
#9 5.388       This package requires Rust and Cargo to compile extensions. Install it through
#9 5.388       the system's package manager or via https://rustup.rs/
#9 5.388
#9 5.388       Checking for Rust toolchain....
#9 5.388       [end of output]
#9 5.388
#9 5.388   note: This error originates from a subprocess, and is likely not a problem with pip.
#9 5.390 error: metadata-generation-failed
#9 5.390
#9 5.390 × Encountered error while generating package metadata.
#9 5.390 ╰─> See above for output.
#9 5.390
#9 5.390 note: This is an issue with the package mentioned above, not pip.
#9 5.390 hint: See above for details.
#9 5.527
#9 5.527 [notice] A new release of pip available: 22.3 -> 22.3.1
#9 5.527 [notice] To update, run: pip install --upgrade pip
------
executor failed running [/bin/sh -c pip install --no-cache-dir -q -r requirements.txt]: exit code: 1

Here are some of the dependencies that I suspect. However, they install correctly on 3.8

orjson==3.5.1
confluent-kafka==1.8.2
snowflake-connector-python==2.8.1

Would love to get your thoughts how you would approach that?

opened by zurferr 0

Update version of fastapi

I noticed this image uses a version of fastapi from about a year ago: fastapi==0.68.1 Are there plans to the update the images version of fastapi? Thank yee.
investigate

opened by lauraerinmann 1

Releases(0.7.0)

0.7.0(Nov 25, 2022)
Highlights of this release:

Support for Python 3.10 and 3.11.

Deprecation of Python 3.6.

The last Python 3.6 image tag was pushed and is available in Docker Hub, but it won't be updated or maintained anymore.

The last image with a date tag is python3.6-2022-11-25.

Upgraded versions of all the dependencies.

Features

✨ Add support for Python 3.10 and 3.11. PR #220 by @tiangolo.

✨ Add Python 3.9 and Python 3.9 Alpine. PR #67 by @graue70.

Breaking Changes

🔥 Deprecate and remove Python 3.6. PR #211 by @tiangolo.

Upgrades

⬆️ Upgrade FastAPI and Uvicorn versions. PR #212 by @tiangolo.

⬆️ Upgrade packages to the last version that supports Python 3.6. PR #207 by @tiangolo.

Docs

📝 Add note to discourage Alpine with Python. PR #122 by @tiangolo.

📝 Add warning for Kubernetes, when to use this image. PR #121 by @tiangolo.

✏ Fix typo, repeated word on README. PR #96 by @shelbylsmith.

Internal

⬆️ Update black requirement from ^20.8b1 to ^22.10. PR #216 by @dependabot[bot].

⬆️ Update docker requirement from ^5.0.3 to ^6.0.1. PR #217 by @dependabot[bot].

🔥 Remove old Travis file. PR #219 by @tiangolo.

⬆️ Upgrade CI OS. PR #218 by @tiangolo.

🔧 Update Dependabot config. PR #213 by @tiangolo.

👷 Add scheduled CI. PR #210 by @tiangolo.

👷 Add alls-green GitHub Action. PR #209 by @tiangolo.

👷 Do not run double CI, run on push only on master. PR #208 by @tiangolo.

⬆️ Bump actions/setup-python from 4.1.0 to 4.3.0. PR #201 by @dependabot[bot].

⬆️ Update black requirement from ^19.10b0 to ^20.8b1. PR #113 by @dependabot[bot].

⬆️ Update docker requirement from ^4.2.0 to ^5.0.3. PR #125 by @dependabot[bot].

⬆️ Bump actions/checkout from 2 to 3.1.0. PR #194 by @dependabot[bot].

⬆️ Update mypy requirement from ^0.770 to ^0.971. PR #184 by @dependabot[bot].

⬆️ Update isort requirement from ^4.3.21 to ^5.8.0. PR #116 by @dependabot[bot].

⬆️ Bump tiangolo/issue-manager from 0.2.0 to 0.4.0. PR #110 by @dependabot[bot].

⬆️ Bump actions/setup-python from 1 to 4.1.0. PR #182 by @dependabot[bot].

⬆️ Update pytest requirement from ^5.4.1 to ^7.0.1. PR #153 by @dependabot[bot].

📌 Add external dependencies and Dependabot to get automatic upgrade PRs. PR #109 by @tiangolo.

👷 Update Latest Changes. PR #108 by @tiangolo.

👷 Allow GitHub workflow dispatch to trigger test and deploy. PR #93 by @tiangolo.

👷 Add latest-changes GitHub action, update issue-manager, add funding. PR #70 by @tiangolo.

Source code(tar.gz)
Source code(zip)
0.6.0(Apr 27, 2020)
Add docs about installing and pinning dependencies. PR #41.

Add slim version. PR #40.

Update and refactor bringing all the new features from the base image. Includes:

Centralize, simplify, and deduplicate code and setup

Move CI to GitHub actions

Add Python 3.8 (and Alpine)

Add new configs and docs:

WORKER_CLASS

TIMEOUT

KEEP_ALIVE

GRACEFUL_TIMEOUT

ACCESS_LOG

ERROR_LOG

GUNICORN_CMD_ARGS

MAX_WORKERS

PR #39.

Disable pip cache during installation. PR #38.

Migrate local development from Pipenv to Poetry. PR #34.

Add docs for custom PRE_START_PATH env var. PR #33.

Source code(tar.gz)
Source code(zip)
0.5.0(Oct 15, 2019)
Refactor tests to use env vars and add image tags for each build date, like tiangolo/uvicorn-gunicorn-fastapi:python3.7-2019-10-15. PR #17.

Upgrade Travis. PR #9.

Source code(tar.gz)
Source code(zip)
0.4.0(Mar 7, 2019)
Add support for live auto-reload with an additional custom script /start-reload.sh, check the updated documentation. PR #6 in parent image.

Source code(tar.gz)
Source code(zip)
0.3.0(Mar 4, 2019)
Set WORKERS_PER_CORE by default to 1, as it shows to have the best performance on benchmarks.

Make the default web concurrency, when WEB_CONCURRENCY is not set, to a minimum of 2 workers. This is to avoid bad performance and blocking applications (server application) on small machines (server machine/cloud/etc). This can be overridden using WEB_CONCURRENCY. This applies for example in the case where WORKERS_PER_CORE is set to 1 (the default) and the server has only 1 CPU core. PR #6 and PR #5 in parent image.

Source code(tar.gz)
Source code(zip)
0.2.0(Mar 4, 2019)
From upstream image: https://github.com/tiangolo/uvicorn-gunicorn-docker

Make /start.sh run independently, reading and generating used default environment variables. And remove /entrypoint.sh as it doesn't modify anything in the system, only reads environment variables. PR #4.

Source code(tar.gz)
Source code(zip)
0.1.0(Feb 8, 2019)

Add support for /app/prestart.sh.
Source code(tar.gz)
Source code(zip)

Docker image with Uvicorn managed by Gunicorn for high-performance FastAPI web applications in Python 3.6 and above with performance auto-tuning. Optionally with Alpine Linux.

Related tags

Overview

Supported tags and respective Dockerfile links

uvicorn-gunicorn-fastapi

Description

Technical Details

Uvicorn

Gunicorn

FastAPI

tiangolo/uvicorn-gunicorn-fastapi

tiangolo/uvicorn-gunicorn

tiangolo/uvicorn-gunicorn-starlette

How to use

Quick Start

Build your Image

Check it

Interactive API docs

Alternative API docs

Dependencies and packages

Using Poetry

Advanced usage

Environment variables

MODULE_NAME

VARIABLE_NAME

APP_MODULE

GUNICORN_CONF

WORKERS_PER_CORE

MAX_WORKERS

WEB_CONCURRENCY

HOST

PORT

BIND

LOG_LEVEL

WORKER_CLASS

TIMEOUT

KEEP_ALIVE

GRACEFUL_TIMEOUT

ACCESS_LOG

ERROR_LOG

GUNICORN_CMD_ARGS

PRE_START_PATH

Custom Gunicorn configuration file

Custom /app/prestart.sh

Development live reload

Details

Usage

Development live reload - Technical Details

Tests

Release Notes

Latest Changes

0.6.0

0.5.0

0.4.0

0.3.0

0.2.0

0.1.0

License

Comments

Add support to install multiple python versions

Improve error handling and messages

Releases(0.7.0)

0.7.0(Nov 25, 2022)

Features

Breaking Changes

Upgrades

Docs

Internal

0.6.0(Apr 27, 2020)

0.5.0(Oct 15, 2019)

0.4.0(Mar 7, 2019)

0.3.0(Mar 4, 2019)

0.2.0(Mar 4, 2019)

0.1.0(Feb 8, 2019)

Owner

Sebastián Ramírez

High-performance Async REST API, in Python. FastAPI + GINO + Arq + Uvicorn (w/ Redis and PostgreSQL).

Simple web app example serving a PyTorch model using streamlit and FastAPI

api versioning for fastapi web applications

A comprehensive CRUD API generator for SQLALchemy.

Supported tags and respective `Dockerfile` links

`tiangolo/uvicorn-gunicorn-fastapi`

`tiangolo/uvicorn-gunicorn`

`tiangolo/uvicorn-gunicorn-starlette`

`MODULE_NAME`

`VARIABLE_NAME`

`APP_MODULE`

`GUNICORN_CONF`

`WORKERS_PER_CORE`

`MAX_WORKERS`

`WEB_CONCURRENCY`

`HOST`

`PORT`

`BIND`

`LOG_LEVEL`

`WORKER_CLASS`

`TIMEOUT`

`KEEP_ALIVE`

`GRACEFUL_TIMEOUT`

`ACCESS_LOG`

`ERROR_LOG`

`GUNICORN_CMD_ARGS`

`PRE_START_PATH`

Custom `/app/prestart.sh`