the atomic command

from a container image to the host

on the host

a systemd

"while still being able"

worth commenting on "what happens if you try to install it twice"?

"Configuration is stored in the same locations on the host as a non-containerized service."

"locations on the host"

"inside the container"

is this true? like will they literally land in the that spot on the host? I thought we had a planned to do a tree under /opt and then sym-link from the "right" spot

this seems a bit out of context and kinda just thrown in ... How about reversing it a bit to be like "We have based standalone containers on the model & technology of system containers. If you would like to know more about system containers read the blog post" or some such?

"by the RPM database"

Updated. Thanks for articularizing me. @eslobodo @langdon @nphilipp

@langdon

is this true? like will they literally land in the that spot on the host? I thought we had a planned to do a tree under /opt and then sym-link from the "right" spot

I'm not aware of that. Current implementation of system containers and standalone containers puts the files on host, so they file-conflict with native services.

$ rpm -ql nginx-container-1-1.noarch
/etc/nginx/fastcgi.conf
/etc/nginx/fastcgi.conf.default
/etc/nginx/fastcgi_params
/etc/nginx/fastcgi_params.default
/etc/nginx/koi-utf
/etc/nginx/koi-win
/etc/nginx/mime.types
/etc/nginx/mime.types.default
/etc/nginx/nginx.conf
/etc/nginx/nginx.conf.default
/etc/nginx/scgi_params
/etc/nginx/scgi_params.default
/etc/nginx/uwsgi_params
/etc/nginx/uwsgi_params.default
/etc/nginx/win-utf
/usr/lib/systemd/system/nginx-container.service
/usr/share/nginx/html/404.html
/usr/share/nginx/html/50x.html
/usr/share/nginx/html/index.html
/usr/share/nginx/html/nginx-logo.png
/usr/share/nginx/html/poweredby.png

no symlinks

LGTM, would like to consider the "/opt" thing at some point but it doesn't block this PR