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

Container not getting added to SkyDNS after retagging #43

Open
3onyc opened this issue Mar 7, 2014 · 4 comments
Open

Container not getting added to SkyDNS after retagging #43

3onyc opened this issue Mar 7, 2014 · 4 comments
Labels

Comments

@3onyc
Copy link
Contributor

3onyc commented Mar 7, 2014

Docker Version: 0.8.1
SkyDock version: Both the latest image from index, and the master branch tried.
SkyDNS version: latest image.

After a container's image ends up untagged (Primary reason, image being rebuilt), and then retagging it SkyDock does not seem to detect the new image name, I've tried the following:

  • Start/stop the container that was re-tagged (Also tried a restart)
  • Restart SkyDock
  • Recreate the SkyDock container

The containers with retagged images:

4c6568f28cdc        internal-old/nginx:latest        /start                 18 hours ago         Up 13 minutes       80/tcp                           restore-test                                                                               
8851c7056f5b        internal-oldold/nginx:latest     /start                 18 hours ago         Up 13 minutes       80/tcp                           satis-test        

The log output from SkyDock on restart is

[info] 1394187898 skydock: adding 450666b2d4 (router) to skydns
[info] 1394187898 skydock: service already exists for 450666b2d4. Resetting ttl.
...
[info] 1394187898 skydock: adding f05a1bdd17 (mysql) to skydns
[info] 1394187898 skydock: service already exists for f05a1bdd17. Resetting ttl.

But no mention of nginx or the above containers.

Stop/starting the containers with retagged images:

[debug] 1394188038 skydock: received event (stop) 8851c7056f5b86fff433cb1ca041fa9888516bd4a0213bd8b350a5bf30b9706b internal-oldold/nginx:latest
[info] 1394188038 skydock: removing 8851c7056f from skydns
[debug] 1394188041 skydock: received event (start) 8851c7056f5b86fff433cb1ca041fa9888516bd4a0213bd8b350a5bf30b9706b internal-oldold/nginx:latest

But no mention of it being added or the name (nginx) being detected.

Querying the SkyDNS server for any of these also returns no results.

@crosbymichael
Copy link
Owner

Ok, i think i see what is going on here

@3onyc
Copy link
Contributor Author

3onyc commented Mar 8, 2014

If you can tell me what you think is going on I could take a swing at fixing it myself, unless you're already working on it.

@3onyc
Copy link
Contributor Author

3onyc commented Apr 28, 2014

Any progress on this?

@samos123
Copy link

Closely related to #40

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

No branches or pull requests

3 participants