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 support for running with private registry #356

Open
vdice opened this issue May 3, 2017 · 1 comment
Open

add support for running with private registry #356

vdice opened this issue May 3, 2017 · 1 comment

Comments

@vdice
Copy link
Member

vdice commented May 3, 2017

Currently e2e tests don't support running on a cluster using a private registry.

To deploy an application on Workflow while using a private registry, the PORT env var needs to be set in the application config before a deploy can occur. E2E doesn't yet attempt to do this, so all such tests will fail with:

...
$ deis apps:create test-661286376 --no-remote
Creating Application... done, created test-661286376
If you want to add a git remote for this app later, use `deis git:remote -a test-661286376`
$ deis builds:create --app=test-661286376 deis/example-dockerfile-http
Creating build... Error: Unknown Error (400): {"detail":"PORT needs to be set in the application config when using a private registry"}
$ deis apps:destroy --app=test-661286376 --confirm=test-661286376
Destroying test-661286376...
done in 2s
...

Filing this issue so it is more readily known and perhaps to actually add support in future!

@Cryptophobia
Copy link

This issue was moved to teamhephy/workflow-e2e#4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants