schroot fails to use files in /etc/schroot/chroot.d/

Bug #605581 reported by Curtis Lee Bolin
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
schroot (Ubuntu)
Fix Released
Undecided
Roger Leigh

Bug Description

Binary package hint: schroot

schroot fails to use the file /etc/schroot/chroot.d/karmic64.conf that I created.

$ schroot -l
W: No chroots are defined in ‘/etc/schroot/schroot.conf’

The manual for schroot says config files in the /etc/schroot/chroot.d/ will be treated the same as /etc/schroot/schroot.conf .

$ man schroot
...
       /etc/schroot/chroot.d
              Additional chroot definitions may be placed in files under this
              directory. They are treated in exactly that same manner as
              /etc/schroot/schroot.conf. Each file may contain one or more
              chroot definitions. Note that the files in this directory fol‐
              low the same naming rules as run-parts(8) when run with the
              --lsbsysinit option.

Thank You For Your TIme

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: schroot 1.4.0-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-23-generic x86_64
Architecture: amd64
Date: Wed Jul 14 14:36:45 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: schroot

Revision history for this message
Curtis Lee Bolin (curtisleebolin) wrote :
Revision history for this message
Curtis Lee Bolin (curtisleebolin) wrote :

updated /etc/schroot/chroot.d/karmic64.conf

[karmic64]
description=Ubuntu 9.10 karmic amd64
directory=/srv/chroot/karmic64
root-users=george
type=directory
users=george

Revision history for this message
Ryan Maki (ryan.maki) wrote :

Try changing the name of your configuration file.

/etc/schroot/chroot.d/karmic64 (remove the .conf)

I had a similar problem with my config files because I named them with underscores. Changing underscores to dashes in the file name and [header] fixed the problem. This may be due to some syntax rules in run-parts(8), I'm not sure.

You can run the following command to get debugging output:

schroot -l -v --debug=notice

HTH

Revision history for this message
Roger Leigh (rleigh) wrote :

Ryan,

This is exactly the cause of the problem. From schroot(1):

       /etc/schroot/chroot.d
              Additional chroot definitions may be placed in files under this
              directory. They are treated in exactly that same manner as
              /etc/schroot/schroot.conf. Each file may contain one or more
              chroot definitions. Note that the files in this directory fol‐
              low the same naming rules as run-parts(8) when run with the
              --lsbsysinit option.

This means the file can't contain '.'s, or appear as though it's an editor backup file or backup dpkg conffile.

The Ubuntu version is outdated WRT Debian, but this documentation was added for 1.4.0.

Regards,
Roger
(upstream author)

Revision history for this message
Roger Leigh (rleigh) wrote :

Update: the naming rules have been relaxed in current stable releases (1.4.16+) so the filenames above will now work correctly again.

Regards,
Roger

Roger Leigh (rleigh)
Changed in schroot (Ubuntu):
status: New → Fix Released
assignee: nobody → Roger Leigh (rleigh)
Revision history for this message
Александр (gg-shaman888) wrote :

$sudo apt-get install schroot
$schroot -c test
terminate called after throwing an instance of 'std::runtime_error'
  what(): locale::facet::_S_create_c_locale name not valid
$export LC_ALL=C
$schroot -c test
W: No chroots are defined in '/etc/schroot/schroot.conf' or '/etc/schroot/chroot.d'

Ubuntu 16.04.05 x64 - the error is reproduced.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.