Closed benjaminvdb closed 5 years ago
Hi @benjaminvdb,
For some reason, your container failed to start. Please, check the logs on the running instance: see the "The instance is failed to start. Where can I find the logs? question in FAQ.
@apls777 Thank you for the incredibly fast reply!
I feel very stupid. I copied the requirements.txt
file to docker
without renaming to requirements-spotty.txt
... Everything is working fine now! Thanks for your help.
Would it be possible to show logs from the Docker container on the local machine easily? The Heroku CLI has real-time tailing with heroku logs --tail
, which is incredibly useful. This idea could work for Spotty as well using a similar approach (display a log file within a container using the tail
command).
There already was a similar feature request (#52), but maybe it's a better idea of how to pull the logs. Thanks!
Glad it's working for you now, I'm then closing the issue.
Hi!
Spotty sounds like an excellent idea and I'm eager to try it out. I'm following this article step-by-step.
At the first step of model training, I'm running into an error after running
spotty start
(for the extended log, see bottom):CloudFormation is showing:
I can run
spotty run ssh
, but this shows a tmux session with the messagePane is dead
. I can close the window usingctrl-b x
and execute commands from there. However, runningspotty run <script>
orspotty run -r <scripts>
gives me the same dead tmux session and the script is not being executed. If possible, I'd like to run Spotty commands from my local machine as advertised. What's going on here and how can I solve it?Thanks!