# Ignition Docker with sql database

**URL:** <https://forum.inductiveautomation.com/t/ignition-docker-with-sql-database/50571>\
**Category:** Ignition\
**Tags:** ignition80\
**Created:** [September 2, 2021, 6:46pm UTC](https://forum.inductiveautomation.com/t/ignition-docker-with-sql-database/50571 "2021-09-02T18:46:33Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\
**Post date:** [March 9, 2023, 2:05pm UTC](https://forum.inductiveautomation.com/t/ignition-docker-with-sql-database/50571/7 "2023-03-09T14:05:03Z")

</div>

I'll also augment that as of Docker Engine 20.10, you can also use `host.docker.internal` mapping on Linux (where it was previously only available on Docker Desktop). You do have to add an `extra_hosts` mapping to your container definition though, such as:

```bash
docker run ... --add-host "host.docker.internal:host-gateway" ...

```

... or in your Compose YAML:

```yaml
services:
  gateway:
    ...
    extra_hosts:
      - "host.docker.internal:host-gateway"
    ....

```

With this, the hostname `host.docker.internal` will resolve to your `docker0` bridge IP on the host.

---

_[View the full topic](https://forum.inductiveautomation.com/t/ignition-docker-with-sql-database/50571)._