Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Strange Service Issue #95

Open
Crispy1975 opened this issue Oct 23, 2015 · 0 comments
Open

Strange Service Issue #95

Crispy1975 opened this issue Oct 23, 2015 · 0 comments

Comments

@Crispy1975
Copy link

We are using SkyDock which works perfectly when we pull down and run pre-built images from our Docker Hub account (via a Bash script using Docker Machine), however when we build images and run them on the fly they do not seem to register with SkyDock/SkyDNS and we do not currently know why. The process is essentially the same...

Pre-built

  1. Start Docker Machine (with daemon dns options etc.).
  2. Run skydock/skydns with the proper options.
  3. Run containers (pull from registry automated)
  4. Run HAProxy in front of it all (container)

Building

  1. Start Docker Machine (with daemon dns options etc.).
  2. Run skydock/skydns with the proper options.
  3. Build images from local Dockerfiles and tag.
  4. Run containers from step 3.
  5. Run HAProxy in front of it all (container).

That's it. Any ideas why the pre-built images would work over the images built on the fly? Surely it should be the same DNS service registration no matter what?

We see lines like this in the SkyDNS logs...

2015/10/23 09:39:45 Error:  Service does not exist in registry

If we then build each image and run manually DNS registers correctly. Initially I thought it might have been a speed thing but I've tried many tests and so far no luck.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant