CODEWITHSUNDEEP
dockercoreosfleet
smeeb
smeeb

Reputation: 29537

Fleet can't launch Docker registry container

I'm brand-spanking-new to Docker and CoreOS. I have a VM running CoreOS as its host, and I'd like to simply get the WordPress container running on it (as a "Hello, Docker/CoreOS!"-type primer.

I found this excellent article which led me to SSH into the CoreOS VM and try:

fleetctl submit https://registry.hub.docker.com/_/wordpress/

But when I run this, I get:

Error creating units: error retrieving Unit(wordpress.service) from Registry: Get http://domain-sock/fleet/v1/units/wordpress.service?alt=json: dial unix /var/run/fleet.sock: no such file or directory

Any ideas as to what I need to do to get the WordPress container running, so that I could got to some URL and actually use it?

Upvotes: 1

Views: 1156

Answers (1)

larsks
larsks

Reputation: 312138

I suspect that fleet is not yet running.

You should probably read through Running CoreOS documentation appropriate to your platform. For example, this document for Vagrant has information about how to configure fleet to start when CoreOS boots, using a "cloud-config" document that is interpreted by cloud-init when the system first boots.

You can start fleetd manually by running:

systemctl start fleet

You will also need to start etcd. Again, the documentation (hopefully!) shows you how to do all of this.

Upvotes: 2

Related Questions