---
schema_version: "1"
id: 892f4a8d313aae3b6a2af5c2495fbc97d49550d87cf71b7e9d4d0d3550d58290
title: Troubleshooting Docker Command Issues
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/gateway/latest/troubleshoot-docker.md
canonical_url: https://docs.mulesoft.com/gateway/latest/troubleshoot-docker
source_site: docs.mulesoft.com
content_type: documentation
content_hash: c8643e29e72b0dab8207d0fa67eda30b9da4e700bb3ea762840ff88f1095824c
description: MuleSoft Documentation Site
release: "1.14"
latest: true
---
---
product: Omni Gateway
version: 1.14
is-latest-version: true
---

# Troubleshooting Docker Command Issues

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Troubleshoot errors returned by a `docker` command:

- [Docker Is Not Started](#daemon-bad-response)

- [Reg Facade Error (400 Bad Request)](#bad-request)

## Docker Is Not Started

If Docker is not started, a `docker` command returns an error message similar to the following ones:

- Error response from daemon: Bad response from Docker engine

- ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon
  running?

If you get this error, start Docker.

## Reg Facade Error (400 Bad Request)

The following error can occur when you use `docker run` to register your gateway:

\[flexctl\]\[error\] reg facade call returned error response: HTTP/1.1 400 Bad Request

The reason for this error is available within the error message. Common causes include:

- `an active target with the same name already exists in this organization and environment`

  To avoid this issue, provide a _unique name_ for your gateway when running the registration
  command. Note that you _cannot reuse the same name_ even if a previous registration with that name
  was successful. When this error occurs, the command generates an _empty_ `registration.yaml`,
  which prevents re-registration _and_ produces an error when you try to use the file when deploying
  the gateway to your cluster.

- `no valid registration token was found`

  To avoid this issue, generate a new token for the command by refreshing the **Add an Omni
  Gateway** page for Kubernetes and rerun the registration command.

## See Also

- [Troubleshooting Request Connection](https://docs.mulesoft.com/gateway/latest/troubleshoot-requests)

- [Troubleshooting with the CLI](https://docs.mulesoft.com/gateway/latest/troubleshoot-admin-api)

- [Setting Up Self-Managed Omni Gateway](https://docs.mulesoft.com/gateway/latest/gateway-set-up)

- [Known Issues](https://help.salesforce.com/s/issues)