You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently DOCKER_HOST is abused to provide portainer and portainer-insuecure "protocols".
Docker, of course, doesn't understand these, and they're only useful for deploying. Usually times, users will want a different docker host to deploy to than to build.
Solution
BELUGA_DEPLOY_HOST will used to deploy when running beluga deploy. If not set, it will default to the value of DOCKER_HOST. It will replace the value of DOCKER_HOST when deploying, including setting DOCKER_HOST when running docker commands.
This will preserve backwards compatibility for users already using DOCKER_HOST, but in documentation, we can remove the sanctioning of abusing DOCKER_HOST.
The text was updated successfully, but these errors were encountered:
Problem
Currently
DOCKER_HOST
is abused to provideportainer
andportainer-insuecure
"protocols".Docker, of course, doesn't understand these, and they're only useful for deploying. Usually times, users will want a different docker host to deploy to than to build.
Solution
BELUGA_DEPLOY_HOST
will used to deploy when runningbeluga deploy
. If not set, it will default to the value ofDOCKER_HOST
. It will replace the value ofDOCKER_HOST
when deploying, including settingDOCKER_HOST
when running docker commands.This will preserve backwards compatibility for users already using
DOCKER_HOST
, but in documentation, we can remove the sanctioning of abusingDOCKER_HOST
.The text was updated successfully, but these errors were encountered: