-
Notifications
You must be signed in to change notification settings - Fork 139
Using systemd unit file for apps shouldn't be considered best practice #151
Comments
There is one issue with this approach, that in case you for example misconfigure container and it exits early during initialization, then what you get with |
I think we should have multiple examples. Including a k8s example. |
Where are the documents written describing best practices? |
@rhatdan I took the following file as the best practice guide: https://github.com/projectatomic/atomic/blob/master/README.md |
There is a Container Best Practices project which should cover those, though it seems a bit frozen (Any comments, @scollier ?:) |
Ok I guess we need to update this to show example of using k8s and docker for starting containers. |
Does anyone have examples of these use cases that I could steal, or even better wanted to send me a pull request to update the examples. |
Never received any other examples so I will close this issue. |
After discussion with @sctweedie we agreed that atomic install example should be rewritten without suggesting to copy the systemd unit file to the host filesystem.
Although this is ok for SPCs which should serve as atomic host extension, it shouldn't be used for applications (like databases) and using
docker run ... --restart=always
inRUN
label should be recommended instead.The text was updated successfully, but these errors were encountered: