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

Set entrypoint to aws #9

Open
shnhrrsn opened this issue Feb 27, 2019 · 1 comment
Open

Set entrypoint to aws #9

shnhrrsn opened this issue Feb 27, 2019 · 1 comment

Comments

@shnhrrsn
Copy link

Any chance you can update to use the entrypoint as aws? It'd be helpful to use with whalebrew which requires it: https://github.com/bfirsh/whalebrew#creating-packages

I'm currently using mesosphere/aws-cli with whalebrew, but it’s not kept up to date and I�’d like to switch :)

Thanks!

@mikesir87
Copy link
Owner

Hi @shnhrrsn! This was actually a deliberate decision to not make aws as the entrypoint. The reasoning was to make it easier to do workflows in CI builds where you might need to get data, use jq to change things, and then send it back to AWS.

However, I think it would be awesome to support whalebrew. One thought I have is to actually turn the Dockerfile into a multi-stage build in which one stage sets the entrypoint. Then, I can update the build to produce two images. Something like this...

  • latest, 1.16.113, etc. - work as is
  • latest-e, 1.16.113-e, etc. - have the entrypoint set.

Basically, any image tags with a -e suffix have the entrypoint set. Thoughts?

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

No branches or pull requests

2 participants