Skip to content
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

feature: support different versions of systemd #68

Open
pires opened this issue Jan 21, 2021 · 12 comments
Open

feature: support different versions of systemd #68

pires opened this issue Jan 21, 2021 · 12 comments
Assignees
Labels
bug Something isn't working documentation Improvements or additions to documentation

Comments

@pires
Copy link
Member

pires commented Jan 21, 2021

For instance, in RHEL7 (systemd 219), user-mode systemd doesn't seem to be a thing. Also, certain unit attributes we populate today are unsupported, such as:

  • BindReadOnlyPaths
  • PrivateMounts
  • ReadOnlyPaths
  • TemporaryFileSystem

I understand older distros may not be a goal but if we want this project to be used on bigger companies, we'll have to account for this.

@pires pires added bug Something isn't working documentation Improvements or additions to documentation labels Jan 21, 2021
@miekg
Copy link
Collaborator

miekg commented Jan 22, 2021

I think most of these are not essential, so we can live without if we detect older systemds. The ReadOnly* ones are nice to have though.

OTOH, even I have access to RHEL8 machines...

@pires pires self-assigned this Jan 22, 2021
@pires
Copy link
Member Author

pires commented Jan 22, 2021

The hard part is to find a feature matrix to determine what attributes are available per version. If we had that, it would be easy to implement this. I need to do some digging because there's demand for RHEL 7 support :)

@miekg
Copy link
Collaborator

miekg commented Jan 22, 2021

Even better would be to probe for support, but harder

@pires
Copy link
Member Author

pires commented Jan 22, 2021

I don't think systemd even does that, does it?

@miekg
Copy link
Collaborator

miekg commented Jan 22, 2021 via email

@pires
Copy link
Member Author

pires commented Jan 22, 2021

I just saw these in journal logs, when parsing the unit, eg

Unknown lvalue 'PrivateMounts' in section 'Service'

@miekg
Copy link
Collaborator

miekg commented Jan 22, 2021 via email

@miekg
Copy link
Collaborator

miekg commented Jan 22, 2021 via email

@miekg
Copy link
Collaborator

miekg commented Jan 22, 2021 via email

@pires
Copy link
Member Author

pires commented Jan 22, 2021

If the CLI does it, then maybe there's an API behind it? I'm not supportive of wrapping CLI because that's not a contract I trust in.

@miekg
Copy link
Collaborator

miekg commented Jan 22, 2021 via email

@miekg
Copy link
Collaborator

miekg commented Jan 23, 2021

Regardless how we probe: this is what I had in mind: #74

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants