So, right now I use a remote docker host (remote meaning a server in my closet) for all my for all my development, since docker4mac is still terrible. This works great, but it means that any container that exposes some service needs to expose it publicly:
ports:
- "0.0.0.0:5601:5601"
elastic-package doesn't seem to like me doing that, as it keeps the config in ~/.elastic-package and it'll blow away any changes I make at will. I don't really feel like mainting my own .yml either. Perhaps we can have elastic-package maybe read some port override from an environment variable or custom dotfile?
So, right now I use a remote docker host (remote meaning a server in my closet) for all my for all my development, since docker4mac is still terrible. This works great, but it means that any container that exposes some service needs to expose it publicly:
elastic-packagedoesn't seem to like me doing that, as it keeps the config in~/.elastic-packageand it'll blow away any changes I make at will. I don't really feel like mainting my own.ymleither. Perhaps we can haveelastic-packagemaybe read some port override from an environment variable or custom dotfile?