Skip to content

Conversation

@leopoldodonnell
Copy link

When using a container, servers within typically need to bind to 0.0.0.0 to expose themselves
externally to the container. This change supports a separate bind address from the container's
IP that needs to be relayed to clair to deliver responses and notifications.

I'm not the original author, so it's not always easy to provide the best answer, I'm open to addressing this differently. This change tries to make a minimal change more or less in keeping with the surrounding code.

…tainer

When using a container, servers within typically need to bind to 0.0.0.0 to expose themselves
externally to the container. This change supports a separate bind address from the container's
IP that needs to be relayed to clair to deliver responses and notifications.
if viper.GetString("clairctl.bind_addr") != "" {
listenOn = viper.GetString("clairctl.bind_addr") + ":" + viper.GetString("clairctl.port")
}
log.Debugf("Listinging on: %s", listenOn)
Copy link
Owner

Choose a reason for hiding this comment

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

there is a typo here: "Listinging"

@jgsqware
Copy link
Owner

Thanks for your contribution. There is a little typo, after you've fixed it, I'll merge the PR

@jgsqware jgsqware force-pushed the master branch 3 times, most recently from 64edd0f to 29a1925 Compare May 29, 2017 09:06
@jdel
Copy link
Collaborator

jdel commented Jul 19, 2017

Is this still required ? clairctl works fine in a container without the need for this fix.

@jgsqware
Copy link
Owner

jgsqware commented Jul 19, 2017 via email

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.

3 participants