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.

Sign up for GitHub

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

Jump to bottom

OMV 7 doesn't install on debian when in an LXC container #1678

Closed
nerdoc opened this issue Jan 9, 2024 · 4 comments · May be fixed by openmediavault/openmediavault-docs#129
Closed

OMV 7 doesn't install on debian when in an LXC container #1678

nerdoc opened this issue Jan 9, 2024 · 4 comments · May be fixed by openmediavault/openmediavault-docs#129
Labels
7.x known issue wontfix

Comments

@nerdoc
Copy link

nerdoc commented Jan 9, 2024 •
edited
Loading

Simply put: OMV 7 doesn't install correctly on Debian when in an LXC container. After installing, chrony doesn't start.

Steps to reproduce: Start an LXC container with Debian, install OMV 7 there (any method)

omv-salt deploy run chrony
----------
          ID: configure_chrony
    Function: file.managed
        Name: /etc/chrony/chrony.conf
      Result: True
     Comment: File /etc/chrony/chrony.conf is in the correct state
     Started: 15:10:42.951022
    Duration: 121.023 ms
     Changes:   
----------
          ID: start_chrony_service
    Function: service.running
        Name: chrony
      Result: False
     Comment: Job for chrony.service failed because the control process exited with error code.
              See "systemctl status chrony.service" and "journalctl -xeu chrony.service" for details.
     Started: 15:10:43.795695
    Duration: 77.767 ms
     Changes:

Expected behavior

chrony should start, even on an LXC container

openmediavault Server (please complete the following information):

Client (please complete the following information):

not applicable

There is a fix on serverfault. I opened a PR to include a hint in the debian install docs.
@nerdoc nerdoc added the bug label Jan 9, 2024
@nerdoc nerdoc mentioned this issue Jan 9, 2024
Open
@ryecoaaron
Copy link
Contributor

ryecoaaron commented Jan 9, 2024 •
edited
Loading

OMV requires real or virtualized hardware. An LXC container does not provide this and is not supported.

@votdev
Copy link
Member

votdev commented Jan 9, 2024

As already mentioned OMV is not designed to run in a container environment and there are no plans to support that.

If chrony can be tweaked by adding the -x argument, this can be done easily by adding it to DAEMON_OPTS in /etc/default/chrony. This file is not under control of OMV, so custom modifications are not overwritten.

@votdev
Copy link
Member

votdev commented Jan 9, 2024

I'm closing this issue because it only affects LXC setups which are not supported by OMV.

@votdev votdev closed this as completed Jan 9, 2024
@nerdoc
Copy link
Author

nerdoc commented Jan 10, 2024

OK, I didn't know that LXC is not supported. Sorry for the spam then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
7.x known issue wontfix
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

add hint for installing debian in an LXC container nerdoc/openmediavault-docs
3 participants
@votdev @ryecoaaron @nerdoc