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

Add ECS_DOCKER_PULL_INACTIVITY_TIMEOUT - Address issue 1396 #1566

Closed
wants to merge 6 commits into from

Conversation

wattdave
Copy link
Contributor

@wattdave wattdave commented Sep 10, 2018

Summary

This pull request enables a new environment variable, ECS_DOCKER_PULL_INACTIVITY_TIMEOUT, in support of working around #1396.

Implementation details

I cloned the existing handling of other kinds of timeouts and applied them to this one, then applied the configured setting so that it was no longer hard-wired to 1 minute.

Testing

go test

  • Builds on Linux (make release)
  • Builds on Windows (go build -out amazon-ecs-agent.exe ./agent)
  • Unit tests on Linux (make test) pass
  • Unit tests on Windows (go test -timeout=25s ./agent/...) pass
  • Integration tests on Linux (make run-integ-tests) pass
  • Integration tests on Windows (.\scripts\run-integ-tests.ps1) pass
  • Functional tests on Linux (make run-functional-tests) pass
  • Functional tests on Windows (.\scripts\run-functional-tests.ps1) pass

New tests cover the changes:
yes

Description for the changelog

Add ECS_DOCKER_PULL_INACTIVITY_TIMEOUT environment variable

Licensing

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@petderek
Copy link
Contributor

Thanks for the pull request! We will probably wait to merge this until after we are done migrating to the official docker sdk (work happening in the moby branch).

@wattdave
Copy link
Contributor Author

wattdave commented Oct 3, 2018

@petderek It looks like no one has done any work in the moby branch in a month now. Any chance of merging this ahead of that being completed?

@petderek
Copy link
Contributor

petderek commented Oct 3, 2018

@wattdave Yes, we hit some snags on the branch -- apologies for the delay. I'll merge this soon and we will get this released in v1.21.0.

@petderek petderek added this to the 1.21.0 milestone Oct 8, 2018
@petderek petderek mentioned this pull request Oct 9, 2018
8 tasks
@petderek
Copy link
Contributor

Thanks again... merged in #1607

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