Skip to content

Fixed #7: Docker-based development of Rig. #8

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

Merged
merged 2 commits into from
Feb 28, 2017
Merged

Conversation

grayside
Copy link
Contributor

As noted in the docker-compose file, I was unable to get the dynamic linking of -cgo compilation to work in the container. However, it does produce a working binary that can do things, I'm just not sure what it fails at right now.

rig dashboard and rig start seemed to work fine.

@grayside
Copy link
Contributor Author

This fixes #7.

@febbraro
Copy link
Member

@grayside Do you think we should remove the cgo compilation for resolving the dnsdock container by domain name and instead inspect the container for IP address and perform the lookup that way?

@grayside
Copy link
Contributor Author

@febbraro If that removes our only dependency on cgo I think it should help avoid some real headaches. Without it you could automate the builds which seems nice.

@febbraro
Copy link
Member

@grayside ok, lets get this merged and I'll open another issue/PR around removing the cgo dependency.

@febbraro febbraro merged commit ac8dc8a into develop Feb 28, 2017
@febbraro febbraro deleted the task/dockerize branch February 28, 2017 19:26
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

Successfully merging this pull request may close these issues.

2 participants