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
The remote will ssh in and end up at the home dir, for example. /root
Currently the stack file is copied to the remote at the deploy_path location. So with a config with deploy_path: /root/my-deployment as in the example, the file will exist here: deploy_path: /root/my-deployment/docker-compose.yml
The script does not handle this. Deployment command is hard coded before the file is placed and only points to it by name
The remote will ssh in and end up at the home dir, for example.
/root
Currently the stack file is copied to the remote at the
deploy_path
location. So with a config withdeploy_path: /root/my-deployment
as in the example, the file will exist here:deploy_path: /root/my-deployment/docker-compose.yml
The script does not handle this. Deployment command is hard coded before the file is placed and only points to it by name
docker-deployment-action/docker-entrypoint.sh
Line 63 in 878e582
This means you will get errors like this if you have it place the files anywhere other than the ssh user's root:
WORKAROUND
Until anything changes, if you are going to copy the files, it looks like you must specify the ssh user's $HOME dir.
The text was updated successfully, but these errors were encountered: