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

quickstart doenst start #77

Closed
JGamboa opened this issue Mar 16, 2021 · 9 comments
Closed

quickstart doenst start #77

JGamboa opened this issue Mar 16, 2021 · 9 comments

Comments

@JGamboa
Copy link

JGamboa commented Mar 16, 2021

Im getting the next log

Successfully built 9ace8a356c94b5b4581b63de7ae42807592f214de87e6f89a281c4479d292e2f
WARNING: The SSH_AUTH_SOCK variable is not set. Defaulting to a blank string.
Creating my_awesome_lambda_my-awesome-lambda_run ... error

ERROR: for my_awesome_lambda_my-awesome-lambda_run Cannot create container for service my-awesome-lambda: invalid volume specification: '.:.:rw': invalid mount config for type "volume": invalid mount path: '.' mount path must be absolute

ERROR: for my-awesome-lambda Cannot create container for service my-awesome-lambda: invalid volume specification: '.:.:rw': invalid mount config for type "volume": invalid mount path: '.' mount path must be absolute
ERROR: Encountered errors while bringing up the project.

I used the quickstart guide, but it didnt event start.-

@JGamboa JGamboa closed this as completed Mar 16, 2021
@metaskills
Copy link
Member

I've seen this recently too. Did you get it sorted out? I had some solutions on my side but wanted to match them up with yours.

@metaskills
Copy link
Member

Are you on Linux?

@JGamboa
Copy link
Author

JGamboa commented Mar 16, 2021

Yes, im using linux, i have the solution but im not sure if is the solution or not, i will try on another clean environment and ill try.

i think that its need the ssh server started.

@metaskills
Copy link
Member

Interesting, I saw this error on GitHub Actions recently. I found when doing COMPOSE_FILE=docker-compose.yml ... where ... is whatever bin script you were running that used docker-compose would help but that did not make sense to me right away since there is only one compose file, no composites.

@metaskills metaskills reopened this Mar 16, 2021
@JGamboa
Copy link
Author

JGamboa commented Mar 16, 2021

i will try tomorrow, today i cant >:D , but i have two thinks that i think that can work, one is the ssh server but i really think it isnt, the principal problem is that doenst find connection with the ssh-agent

@JGamboa
Copy link
Author

JGamboa commented Mar 16, 2021

if im not wrong this make it work

eval ssh-agent

@JGamboa
Copy link
Author

JGamboa commented Mar 16, 2021

imagen

@metaskills
Copy link
Member

Thanks! I will be removing the SSH_AUTH_SOCK stuff from the Lamby starter. If anyone needs the SSH stuff they can add it back for local deploys or even using Github Actions with these patterns. https://dev.to/aws-heroes/serverless-docker-patterns-4g1p#crossplatform-ssh-agent-for-cicd

@metaskills
Copy link
Member

Updated the starter (rails-lambda/lamby-cookiecutter#10) which has changes that make working with Linux a little easier. The starter now also removes the SSH stuff and the guides (https://lamby.custominktech.com/docs/bin_scripts_build_and_deploy#using-private-gems-on-github) link to that article. If there is anything you think we should add to the guides or the article, please let me know. Was not able to reproduce your issue locally so I need a bit of help there. Likewise if the current methods work for you, let me know. Thanks!

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