-
Notifications
You must be signed in to change notification settings - Fork 36
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
Docker container exiting with error 255 #6
Comments
@AndrewBreyen I am having the same issue, did you ever resolve it? |
Hi @roblatour and @AndrewBreyen, really sorry I haven't replied in... checks thread.. 2 years... Between some personal reasons and not using this container anymore for my personal use, I haven't been able to maintain it and it's gone stale. If either of you would like ownership of the repo, I can transfer it to you for development. Just let me know. |
@shuaiscott unfortunately I don't know enough about the language (Perl script?) the program is written in to support it. However, thank you for putting this together - it is working fine for me other than the periodic fail, and which when it happens I can simply restart it to get it going again. I see there is an open pull request, I don't know if that would resolve the issue - or if setting the docker contain to restart if it fails - would solve the issue. But in any case thanks again for making this available. If you can't find a new owner for it no worries from my perspective - and I'm sure others would be happy to use it as is as do I. Cheers. |
Hello, I have created the docker container using command
docker run -d --name zap2xml -v /Users/Shared/xmltvdata:/data -e [email protected] -e PASSWORD=password -e OPT_ARGS="-I -D -Z 12345(my zip code)" -e XMLTV_FILENAME=xmltv.xml shuaiscott/zap2xml
The last few lines when done are
However, it exits with (255) status, and it doesnt seem to be starting back up in 12 hours.
Is the exit code expected? If I click the "start" button, it will start up and successfully update the xmltv.xml file, but its not doing it automatically.
The text was updated successfully, but these errors were encountered: