Troubleshooting Docker Command Issues

Troubleshoot errors returned by a docker command:

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.

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.