SocketCluster / SocketCluster/socketcluster
deploy error: accepts at most 1 arg(s), received 3 - docker login ?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6.2k
- Forks
- 318
- PR merge metrics
- No merged PRs in 30d
Description
Hi Jonathan:
When deploying with ssocketcluster deploy I get an error after image is built. it fails at 'docker login' apparently:
=> exporting to image 0.0s
=> => exporting layers 0.0s
=> => writing image sha256:145631044140023b405ff54e34796fb85a2a12f35ccad22 0.0s
=> => naming to docker.io/ciliconherve/signal-skytalk:v1.0.0 0.0s
accepts at most 1 arg(s), received 3
[Error] Failed to deploy the 'signal-skytalk' app. Command failed: docker login -u "...myid" -p "...mypassword"; docker push
ciliconherve/signal-skytalk:v1.0.0
If I run the docker login command by itself, it succeeds (with a warning:
docker login -u "...myid" -p "...mypassword"
WARNING! Using --password via the CLI is insecure. Use --password-stdin.
Login Succeeded
PROBLEM:
I never had this issue before (we have used socketcluster for last one year - works great by the way !) and I searched online and do not seem to find where this come from.
Also I am able to run these 2 commands manually:
docker login -u "...myid" -p "...mypassword"
docker push ciliconherve/signal-skytalk:v1.0.0
ALTERNATIVE FIX:
Would you have the list of commands to perform 'socketcluster deploy' manually so that I can perform the initial deploy manually and hopefully the 'socketcluster update' will work ?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing socketcluster deploy with the Docker image and credentials described in the report, then compare its generated docker login and docker push commands with the manually successful commands. Done means the deploy command completes without the argument error and pushes the built image successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, javascript
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100