-
Notifications
You must be signed in to change notification settings - Fork 119
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
docker version #19
Comments
Hi @rjschwei, We intentionally and explicitly tie the version of ecs-init to our latest tested version of Docker. Currently, the latest version of Docker available in the Amazon Linux AMI's yum repositories is 1.6.2. While we believe that ecs-init (and our Agent) should work without changes on newer versions of Docker, we want to verify that it continues to work before we change the spec file. Does that help answer your question? Thanks! |
On 08/11/2015 12:43 PM, Samuel Karp wrote:
Yes, but leads to a follow on question. Is there a process by which we Do the tests that are part of the source code cover this or are there Thanks, Robert Schweikert MAY THE SOURCE BE WITH YOU |
I've pushed a set of functional tests to the Edit: Fixed some incorrect policy actions. |
On 08/11/2015 03:13 PM, Samuel Karp wrote:
Great, thanks. Will not get to this right away thus I might come back Thanks for the help, Robert Schweikert MAY THE SOURCE BE WITH YOU |
Awesome. I'm going to close this for now, but feel free to either re-open or open a new issue when you have future questions. |
I tried to run the tests from the dev branch on our ecs instance with docker 1.7, however I have problems running the tests because of a missing go package requirement. I got the following:
anything I did wrong here ? Thanks |
It looks like you didn't check out the package into your |
Also, note that my comment above about tests is referring to the ECS Agent repo rather than this repo, and that the tests have been merged into |
ok great that solves it, I checked it out to ~/golang/src/github.com/aws/amazon-ecs-agent when running the tests I got some error but this is due the environment as you mentioned. I'm looking into this now but might come back with further questions if that's ok for you ? Thanks for your help |
I called
and got:
docker runs on this host
and the testing procedure already communicated with docker, a new registry container was started
An already running ecs-agent should not conflict with the testing, should it ? |
Thanks for reporting; it looks like |
The make test target on my system is complaining as follows:
However the cover tool is provided and in the path
I didn't dive deeper into this because I'm actually most interested in the functional tests. Thus I started 'make run-functional-tests' which is still running. In my ecs-functional-test cluster I can see Thanks |
Hmm run-functional-tests failed with
When I called the tests I saw that a new container was registered in the ecs-functional-test cluster Sorry still no luck |
@schaefi What was the policy attached to your instance when you tried With respect to the cover tool, which version of Go are you using? It looks like the version of Go you have installed expects the cover tool to be located at |
Here is the role policy I have setup according to your information:
The go version installed is
|
Thanks. It looks like my original comments were slightly wrong. You'll want to change If I remember correctly, the cover tool changed between Go 1.3 and 1.4. If you don't want to upgrade Go versions, you should still be able to have it function correctly by removing the |
Hey good news, tests passed now :) Thanks a ton for your help I would never have found out these role setup |
Great! Please let us know if you need any more help. |
This allows the customer to specify the name of a custom IAM Role as the instance role for their EC2 Instance Profile. NOTE: If the correct IAM Policy (`AmazonEC2ContainerServiceforEC2Role`) is not attached to the custom instance role, the create cluster command will succeed but no instances will be launched. If a custom role is specified, the `capability-iam` flag is not needed. Closes aws#19. ```sh $ make test ``` ```sh $ ecs-cli up --keypair my-keypair --size 2 --cluster my-test-cluster --role ecsInstanceRole ``` ```sh $ ecs-cli up --keypair my-keypair --size 2 --cluster my-test-cluster --instance-role foo --capability-iam => ERRO[0000] Error executing 'up': Cannot specify custom role when '--capability-iam' flag is set $ ecs-cli up --keypair my-keypair --size 2 --cluster my-test-cluster => ERRO[0000] Error executing 'up': You must either specify a custom role with the '--instance-role' flag or set the '--capability-iam' flag ```
Hi,
More of a question than an issue. The spec (packaging/amazon-linux-ami/ecs-init.spec) file contains:
Requires: docker >= 1.6.0, docker <= 1.6.2
Is there a reason newer versions of docker will not work. Given that docker has not had any backward incompatible changes it appears that
Requires: docker >= 1.6.0
should be sufficient.
Thoughts?
The text was updated successfully, but these errors were encountered: