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

Update docker-compose for local dev #445

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Update docker-compose for local dev #445

wants to merge 2 commits into from

Conversation

Mark-Powers
Copy link
Contributor

No description provided.

Copy link
Contributor

@msherman64 msherman64 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

overall lgtm, just unsure about the 127.0.0.1 removal for ports.

Comment on lines 109 to 111
EDGE_OS_APPLICATION_CREDENTIAL_ID=<grab this from chi@edge keystone>
EDGE_OS_APPLICATION_CREDENTIAL_SECRET=<grab this from chi@edge keystone> No newline at end of file
EDGE_OS_APPLICATION_CREDENTIAL_SECRET=<grab this from chi@edge keystone>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AFAIK this is for the chi@edge resource calendar, I'm assuming we don't test this in local dev yet.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what required the change from 127.0.0.1 to leaving the IP out?
AFAIK docker defaults to "listen on all addresses", did this need to be accessible externally to the local dev machine? Are there any security issues?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Correct. Since this config was intended for use on a KVM with access via sshuttle, it no longer can bind to just 127.0.0.1.

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