Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Why has the crontab been moved out of the docker container?
See original GitHub issueHi everyone,
I just pulled the latest version and realized, that for Docker usage, the docker-compose and Dockerfile have changed. As far as i understand it, it is intended that the crontab is run on the Dockerhost, which executes a docker exec to run the update script inside the container. Why has this implementation been choose?
This goes completely against the docker concept. When I run docker-compose up I want everything that is related and neccessary for that container to be in there as well as all of it removed when I run docker-compose down
Cheers Fabian
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I actually wondered why it is being run via exec + docker-compose service in the first place. Is there a reason why we can’t simply have a standalone docker image?
See “usage with docker” in the readme: https://github.com/Callum17/noip-renew https://github.com/loblab/noip-renew/pull/29/commits
Merged PR of @Callum17 . thanks.