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

Fixed some issues with expose, port mapping, and environment variables #476

Merged
merged 4 commits into from
Nov 20, 2015

Conversation

cbednarski
Copy link
Contributor

  • Port mapping now works for reserved ports as well as dynamic ports
  • Environment variables were being set twice in two different ways; now they are only set once
  • Comprehensive tests for exposed ports, forwarded ports, and environment variables
  • Cleaned up / DRYed up a lot of test code
  • Flattened []map[string]int to map[string]int

- Port mapping now works for reserved ports as well as dynamic ports
- Environment variables were being set twice in two different ways; now they are only set once
- Comprehensive tests for exposed ports, forwarded ports, and environment variables
- Cleaned up / DRYed up a lot of test code
containerPortInt := port.Value

// If the user has mapped a port using port_map we'll change it here
if len(driverConfig.PortMap) == 1 {
Copy link
Contributor

Choose a reason for hiding this comment

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

Does it makes sense to do > 0, and choose the first block?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

the first block is always 0. If we're worried about multiple port_map entries we should normalize this instead.

@cbednarski
Copy link
Contributor Author

The test appears to be failing on docker client detection. I'm not sure how this is related to this change, though.

cbednarski added a commit that referenced this pull request Nov 20, 2015
Fixed some issues with expose, port mapping, and environment variables
@cbednarski cbednarski merged commit 61aeace into master Nov 20, 2015
@cbednarski cbednarski deleted the b-docker-expose branch November 20, 2015 22:28
@diptanu
Copy link
Contributor

diptanu commented Nov 27, 2015

Fixes #507

benbuzbee pushed a commit to benbuzbee/nomad that referenced this pull request Jul 21, 2022
* modify `TestRaft_RemoveFollower` to check removed node state

* add test to verify that a removed node is not able to vote

* do not transition to `Candidate` state if not part of stable configuration

* add some comments to the tests

* do not return if not transitioning state

* add wait loop to test

* remove test related to removed node voting

* check `inConfig` instead of `hasVote`

* updating warn log message to be more accurate
@github-actions
Copy link

github-actions bot commented May 2, 2023

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 2, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants