<html>
    <head>
      <base href="https://bugs.freedesktop.org/" />
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - boot repair tools fail in systemd-nspawn"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=90349">90349</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>boot repair tools fail in systemd-nspawn
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>systemd
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>unspecified
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>x86-64 (AMD64)
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>Linux (All)
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>normal
          </td>
        </tr>

        <tr>
          <th>Priority</th>
          <td>medium
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>general
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>systemd-bugs@lists.freedesktop.org
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>westlake2012@videotron.ca
          </td>
        </tr>

        <tr>
          <th>QA Contact</th>
          <td>systemd-bugs@lists.freedesktop.org
          </td>
        </tr></table>
      <p>
        <div>
        <pre>the systemd-nspawn tool used as chroot works as expected using '-b -D /mnt' but
for some reason grub-install is failing. 

I think this is important because people occasionally use grub-install to fix
boot-up issues. boot repair tools should also work in systemd containers, if
not then a capability needs to be added for this to be possible.

I'm starting to look more into using system-nspawn as an alternative to chroot
since it is easier to repair both script and bootloader issues in just one
container environment.(i'd have to exit systemd-nspawn then reissue mount
commands to setup the chroot environment)

(L.P if you're reading this, then you might want to look into this additional
capability of support for boot repair tools to work compatible in
systemd-nspawn
You mention system-nspawn as an alternative to chroot, 
<a href="http://0pointer.net/blog/projects/changing-roots.html">http://0pointer.net/blog/projects/changing-roots.html</a>
)

thanks</pre>
        </div>
      </p>
      <hr>
      <span>You are receiving this mail because:</span>
      
      <ul>
          <li>You are the QA Contact for the bug.</li>
          <li>You are the assignee for the bug.</li>
      </ul>
    </body>
</html>