« Back to projectatomic.io
Ask Your Question

Starting conatiners at boot

asked 2015-07-13 22:58:13 +0000

schotty gravatar image

updated 2015-07-13 23:06:15 +0000

Greetings! I am actually using RHEL Atomic.

The issue I am having is that I have several containers that I would like started at boot. Is there a specific method I should utilize to accomplish this? On dedicated CentOS/RHEL server installs, I just use systemd, but with os-tree these changes are disappearing on me. Any tips here would be appreciated.

Thanks, Andrew.

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2015-07-21 21:27:30 +0000

jasonbrooks gravatar image

Systemd service files should do it. Here are two examples of starting stuff automatically in atomic hosts w/ systemd:



If your service files aren't surviving between reboots, it may be that you're running the rpm-ostree upgrade, then adding the service files under /etc, and then rebooting? I believe that changes to /etc must be made before an upgrade, or following a post-upgrade reboot, to ensure that they stick around.

edit flag offensive delete link more


Thanks that did the trick. I must have updated and not restarted the system prior to adding in the systemd service files. Works perfect now.

schotty ( 2015-07-30 12:18:49 +0000 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

[hide preview]

Question Tools

1 follower


Asked: 2015-07-13 22:58:13 +0000

Seen: 241 times

Last updated: Jul 21 '15