Fiware云Docker安装时Docker daemon报错求助

Hey there, sorry to hear you're stuck with this Docker daemon error while setting up your Docker host on FIWARE Cloud—let’s walk through some practical fixes since you’re new to both tech stacks.

1. Fix Your Truncated docker-machine Command #

Your command cuts off at --openstack-s...—this is likely a missing critical parameter for the OpenStack driver. For example, you probably need to specify a security group that allows Docker daemon traffic:

• First, create a security group in your FIWARE Cloud dashboard (e.g., named docker-host) that opens:
  • TCP port 22 (for SSH access)
  • TCP port 2376 (the default Docker daemon port used by docker-machine)
• Then add this to your command: --openstack-sec-groups "docker-host"

Double-check all other parameters too—make sure you haven’t missed required flags (like credentials, often set via environment variables such as OS_USERNAME, OS_PASSWORD instead of command flags).

2. Switch to a Newer Ubuntu Image #

You’re using base_ubuntu_14.04, which is quite outdated. Newer Docker versions may not support this legacy OS release, as it lacks modern kernel modules or dependencies needed for the Docker daemon to run. Try switching to a newer Ubuntu image available in FIWARE Cloud (like base_ubuntu_18.04 or base_ubuntu_20.04)—this is one of the most common fixes for daemon startup failures on old distros.

3. Check Floating IP Pool Availability #

The --openstack-floatingip-pool="public-ext-net-01" flag relies on having available floating IPs in that pool. If the pool is exhausted, your Docker host won’t get a public IP, and docker-machine will fail to connect to the daemon. Head to your FIWARE Cloud dashboard to confirm there are unused floating IPs in the pool.

4. Inspect Docker Daemon Logs Directly on the Host #

If the VM was partially created (even if the daemon failed), SSH into it using docker-machine ssh <your-machine-name> and check the Docker logs:

• For Ubuntu 14.04 (which uses Upstart), run:

  cat /var/log/docker.log
  

• Look for specific errors like missing dependencies, port conflicts, or kernel module issues—this will give you the exact root cause instead of a generic "daemon error".

5. Update docker-machine for OpenStack Compatibility #

Older versions of docker-machine may have compatibility bugs with the OpenStack release running on FIWARE Cloud. Download the latest stable version of docker-machine and try your command again—this often resolves driver-specific glitches.

内容的提问来源于stack exchange，提问作者Maria