I run the command

$ sudo debootstrap --variant=buildd --arch i386 lucid /var/chroot/ https://mirror.internet.asn.au/pub/ubuntu/archive/ 

and the error is:

I: Retrieving InRelease 
I: Retrieving Release 
E: Failed getting release file https://mirror.internet.asn.au/pub/ubuntu/archive/dists/lucid/Release 

I've tried with other mirrors too. I've also read the similar issue , but I don't understand the answer?

I'm writing a bash command to deploy gluster inside a chroot called [glusterchroot](https://gitlab.com/infrastructure24/glusterchroot) . I'm having issues mounting files from the host to the chroot. Schroot's man page recommends the following:

$ man schroot.conf | grep -A4 setup.fstab=
    setup.fstab=filename
            The filesystem table file to be used to mount filesystems within the chroot.  The format of this file is the same as for /etc/fstab, documented in fstab(5).  The  only  difference  is
            that  the  mountpoint  path fs_dir is relative to the chroot, rather than the root.  Also note that mountpoints are canonicalised on the host, which will ensure that absolute symlinks
            point inside the chroot, but complex paths containing multiple symlinks may be resolved incorrectly; it is inadvisable to use nested symlinks as mountpoints.

But when I try use this configuration value in /etc/schroot/chroot.d/glusterchroot.conf, the directories don't seem to be mounted. Is there something else I need to add to get this to work? # Configuration Contents of /etc/schroot/chroot.d/glusterchroot.conf:

user@computer:~$ cat /etc/schroot/chroot.d/glusterchroot.conf
#
#
[glusterchroot]
description=Gluster server chroot
directory=/srv/glusterchroot
root-users=root
setup.fstab=glusterchroot/fstabfile
root-groups=root

contents of /etc/schroot/glusterchroot/fstabfile:

user@computer:~$ cat /etc/schroot/glusterchroot/fstabfile 
/run/udev /run/udev none bind,create=file 0 0
sys /sys sysfs defaults 0 1
proc /proc proc defaults 0 0
/dev/ /dev none bind,create=file 0 0
/run/lvm /run/lvm none bind,create=file 0 0
/run/udev /run/udev none bind,create=file 0 0

glusterchroot info:

user@computer:~$ schroot -i -c glusterchroot
  ─── Chroot ───
  Name                   glusterchroot
  Description            Gluster server chroot
  Type                   plain
  Message Verbosity      normal
  Users                  
  Groups                 
  Root Users             root
  Root Groups            root
  Aliases                
  Preserve Environment   false
  Default Shell          
  Environment Filter     ^(BASH_ENV|CDPATH|ENV|HOSTALIASES|IFS|KRB5_CONFIG|KRBCONFDIR|KRBTKFILE|KRB_CONF|LD_.*|LOCALDOMAIN|NLSPATH|PATH_LOCALE|RES_OPTIONS|TERMINFO|TERMINFO_DIRS|TERMPATH)$
  Run Setup Scripts      false
  Configuration Profile  default
  Script Configuration   
  Session Managed        false
  Session Cloned         false
  Session Purged         false
  Path                   /srv/glusterchroot
  Directory              /srv/glusterchroot
  Personality            undefined
  User Modifiable Keys   
  Root Modifiable Keys   
  User Data              
    setup.config         default/config
    setup.copyfiles      default/copyfiles
    setup.fstab          glusterchroot/fstabfile
    setup.nssdatabases   default/nssdatabases

Note, I've also tried using the default setup.fstab in /etc/schroot/default/fstab which also has the same problems stated below. # Problem ls of mounted directories from within the chroot:

user@computer:~$ sudo schroot -d / -c glusterchroot -- ls /
bin  boot  dev  etc  home  lib  lib64  media  mnt  opt  proc  root  run  sbin  srv  sys  tmp  usr  var
user@computer:~$ sudo schroot -d / -c glusterchroot -- ls /proc
user@computer:~$ sudo schroot -d / -c glusterchroot -- ls /run
lock  mount
user@computer:~$ sudo schroot -d / -c glusterchroot -- ls /sys

Example of command that requires these mounts:

user@computer:~$ sudo schroot -d / -c glusterchroot -- findmnt
findmnt: can't read /proc/mounts: No such file or directory

ls of the same directories from the host:

user@computer:~/Documents/gitRepos/generalK8s/glusterchroot$ ls /proc
1     1186  188   233   2541  2719  2864  3548   4     503    76879  903    96          driver         mdstat         thread-self
10    12    19    2334  2551  2720  2909  3549   40    506    777    90370  96493       dynamic_debug  meminfo        timer_list
100   1223  192   2338  2557  2721  2941  3551   404   507    778    904    96522       execdomains    misc           tty
101   124   1942  234   2561  2722  2965  3565   41    508    782    905    96847       fb             modules        uptime
1017  1254  1964  2344  2570  2723  2997  35710  4194  59014  784    906    97          filesystems    mounts         version
1019  1266  197   2362  2579  2724  3     3581   42    59433  787    907    98          fs             mtrr           version_signature
103   127   2     2366  2580  2725  30    3593   43    59435  788    910    99          interrupts     net            vmallocinfo
1032  13    20    24    2589  2726  3049  36     435   59541  8      913    acpi        iomem          pagetypeinfo   vmstat
1047  135   21    2427  26    2728  3052  3613   4358  6      83498  914    asound      ioports        partitions     zoneinfo
105   14    22    2444  2664  2737  3057  3629   4380  60307  86954  915    bootconfig  irq            pressure
106   15    2268  2477  2668  2743  3075  3639   44    60565  87016  91540  buddyinfo   kallsyms       schedstat
109   157   2281  2484  2678  2747  31    3640   4417  60773  87483  916    bus         kcore          scsi
11    16    2282  2487  2683  2748  3124  367    4498  68293  87490  917    cgroups     keys           self
110   1777  2288  25    2699  2785  32    3676   45    68316  87498  919    cmdline     key-users      slabinfo
1110  18    2289  2500  27    28    3220  37     471   70459  877    92     consoles    kmsg           softirqs
1111  1827  2290  2517  2701  2811  3234  3757   4792  75503  880    920    cpuinfo     kpagecgroup    stat
113   1848  2300  2524  2712  2812  3265  3768   4824  76661  881    922    crypto      kpagecount     swaps
114   185   2310  2525  2714  282   33    3784   4835  76738  883    93     devices     kpageflags     sys
115   186   2321  2532  2716  2821  34    38     4842  76855  884    93656  diskstats   loadavg        sysrq-trigger
1184  187   2329  2537  2717  2830  3545  39     5     76873  89805  94     dma         locks          sysvipc
user@computer:~/Documents/gitRepos/generalK8s/glusterchroot$ ls /sys
block  bus  class  dev  devices  firmware  fs  hypervisor  kernel  module  power
user@computer:~/Documents/gitRepos/generalK8s/glusterchroot$ ls /run
acpid.pid      crond.pid        docker.sock  log             openvpn-client  screen             spice-vdagentd    udev
acpid.socket   crond.reboot     fsck         lvm             openvpn-server  sendsigs.omit.d    sshd              udisks2
alsa           cups             gdm3         motd.d          plymouth        shm                sshd.pid          user
avahi-daemon   dbus             gdm3.pid     mount           pppconfig       sm-notify.pid      sudo              utmp
blkid          dmeventd-client  initctl      netns           rpcbind         snapd              systemd           uuidd
console-setup  dmeventd-server  initramfs    network         rpcbind.lock    snapd-snap.socket  thermald          vpnagentd.pid
containerd     docker           irqbalance   NetworkManager  rpcbind.sock    snapd.socket       tmpfiles.d        wpa_supplicant
credentials    docker.pid       lock         openvpn         rpc_pipefs      speech-dispatcher  ubuntu-advantag

This is a typical schroot.conf configuration I use:

[label]
description=whatever
type=directory
personality=linux
preserve-environment=true
directory=/wherever
users=UserForSchrootOnly
profile=desktop_no_tmp

No root-users directive. Separate home directories for schroot env, not using host's /home. I login with host OS's UserForSchrootOnly user to these schroot environments. I usually add this user to the /etc/sudoers.d/someConf file **inside** schroot, with a line,

UserForSchrootOnly ALL=(ALL:ALL) ALL

One of my goals of this setup is to have a quite isolated environment (not for audit kind of strict isolation, but efficient in practice), both through schroot and by using an OS user only for this purpose and nowhere else. On the other hand, for practical reasons it's much easier to have this dedicated user to be sudoer also, inside the schroot env of course. A use case is to run an untrusted closed source app. My concern is: Since UserForSchrootOnly user is a sudoer inside the schroot env, is it possible to be any compromise of security for the host system due to this? Any way to use sudo elevation inside schroot env, to access something outside of schroot or outside UserForSchrootOnly's home dir on the host system? Man page of schroot.conf mentions that root access to chroot is a serious risk; I'm not concerned about user's misbehaviour. My concern is about the untrusted, closed source app, taking advantage of the sudoer user it runs. ___ I'd like to point out that although this seems like an ideal scenario for a sandbox like firejail, I've failed to run some apps with it, even adding the --no-profile parametre. Also other scenarios include apps that need more recent libs, so I need to setup a Debian Testing or Ubuntu schroot env to run the untrusted app inside.

I created the chroot with schroot following these instructions: https://wiki.winehq.org/Building_Wine#Chroot Then to test it I did:

$ sudo mkdir /TestA
$ echo abc |sudo tee /TestA/tst.txt

$ cat /TestA/tst.txt
abc

$ ls -ld /TestA /TestA/tst.txt
drwxr-xr-x 2 root root 4096 Sep 17 03:02 /TestA
-rw-r--r-- 1 root root    4 Sep 17 03:02 /TestA/tst.txt

$ sudo mkdir /srv/chroot/ubuntu_i386/TestB/
$ sudo mount -o bind /TestA/ /srv/chroot/ubuntu_i386/TestB/
$ mount |grep Test
/dev/mapper/MyLvmGroup-something on /srv/chroot/ubuntu_i386/TestB type ext4 (rw,relatime,errors=remount-ro)

$ schroot -c ubuntu_i386 -u root
$ ls -ld /TestB /TestB/tst.txt
ls: cannot access '/TestB/tst.txt': No such file or directory
drwxr-xr-x 2 root root 4096 Sep 17 06:10 /TestB
$ ls -l /TestB
total 0

I tried it also in a non LVM partition as the bind source, and it did not work. What is happening? everywhere ppl saying it works, why it is not working here? what am I missing? ubuntu 20.04

we're trying to implement an initramfs with the intent of: Open a LUKS partition (using a key saved on TPM) Mounting the partition RO Mounting an OverlayFS switch_root to the new system The first part of the script seems to work fine. Our problem is in the "switch_root" part which ends in a kernel panic. Please note that we have the same problem also without the encryption/overlay part. The problem seems strictly related to the switch_root. We are using Yocto Sumo and the initramfs image is bundled with the kernel. Please find attached the kernel panic log. bash-4.4# exec switch_root /newroot /sbin/init BusyBox v1.27.2 (2020-05-20 09:00:12 UTC) multi-call binary. Us[ 593.127118] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100 [ 593.127118] age: switch_root [-c [/ d e59v3/.137247] CPU: 1 PID: 1 Comm: init Tainted: G W 4.14.98+g80655a2d3532 #1 [ 593.147478] Hardware name: Engicam i.Core MX8MM module (DT) onsole] N[E W _5R9O3O.T1 5N3E0W8_] Call trace: [ 593.157367] [] dump_backtrace+0x0/0x3c8 [ 593.162798] [] show_stack+0x14/0x20 INIT [ARGS] [ 593.167891] [] dump_stack+0x9c/0xbc [ 593.174075] [] panic+0x11c/0x28c [ 593.178902] [] complete_and_exit+0x0/0x20 [ 593.184495] [] do_group_exit+0x38/0xa0 [ 593.189828] [] __wake_up_parent+0x0/0x28 [ 593.195338] Exception stack(0xffff00000805bec0 to 0xffff00000805c000) [ 593.201800] bec0: 0000000000000001 0000000000000001 0000000000000001 0000ffffa819b700 [ 593.209644] bee0: 0000000000000020 0000ffffcb90abc8 0000000000010000 0000ffffa81a4a18 [ 593.217490] bf00: 000000000000005e fffffffffffffff0 0101010101010101 0000000000000000 [ 593.225336] bf20: 0101010101010101 00000000004f2f10 0000ffffa7fe92c8 0000ffffa7fdbde0 [ 593.233184] bf40: 0000ffffa7fd7028 0000ffffa800cb68 00000000000005c2 0000000000000008 [ 593.241030] bf60: 0000000000000008 0000ffffa8122bb8 0000000000000001 0000ffffa8125000 [ 593.248874] bf80: 0000ffffa81265a0 0000ffffa81a3738 0000000000000001 0000000000000000 [ 593.256719] bfa0: 0000ffffa812a000 0000ffffcb90ac70 0000ffffa800c7f0 0000ffffcb90ac70 [ 593.264564] bfc0: 0000ffffa807946c 0000000060000000 0000000000000001 000000000000005e [ 593.272408] bfe0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 [ 593.280259] [] el0_svc_naked+0x34/0x38 [ 593.285620] SMP: stopping secondary CPUs [ 593.290003] Kernel Offset: disabled [ 593.293520] CPU features: 0x080200c [ 593.297028] Memory Limit: none [ 593.300135] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100 [ 593.300135] Thanks!

I have access to a Ubuntu system which is like this: $ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT [...] sda 8:0 0 1.8T 0 disk └─sda1 8:1 0 1.8T 0 part /mnt/dbc64c37-340a-49e5-8184-a69e01e5e231 nvme0n1 259:0 0 477G 0 disk ├─nvme0n1p1 259:1 0 650M 0 part /boot/efi └─nvme0n1p2 259:2 0 372.5G 0 part / I have setup a Debian/sid schroot like this: $ cat /etc/schroot/chroot.d/sid64 [sid64] description=Contains the SPICE program aliases=sid type=directory directory=/home/malat/schroots/sid-root users=malat root-groups=root profile=desktop personality=linux preserve-environment=true I have not changed anything to /etc/schroot/default/fstab, and when going inside my schroot sid64 here is what I see: $ schroot -c sid (sid64)$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT [...] sda 8:0 0 1.8T 0 disk └─sda1 8:1 0 1.8T 0 part nvme0n1 259:0 0 477G 0 disk ├─nvme0n1p1 259:1 0 650M 0 part └─nvme0n1p2 259:2 0 372.5G 0 part /var/lib/dbus If I manually do: $ sudo mount /dev/sda1 /mnt/dbc64c37-340a-49e5-8184-a69e01e5e231 $ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 1.8T 0 disk └─sda1 8:1 0 1.8T 0 part /mnt/bdc64c37-340a-49e5-8184-a69e01e5e231 nvme0n1 259:0 0 477G 0 disk ├─nvme0n1p1 259:1 0 650M 0 part └─nvme0n1p2 259:2 0 372.5G 0 part /var/lib/dbus How can I automatically mount /mnt/dbc64c37-340a-49e5-8184-a69e01e5e231 under my schroot (this is my main disk where my data is located) ? --- So far I tried a naive: $ sudo mkdir /home/malat/schroots/sid-root/mnt/dbc64c37-340a-49e5-8184-a69e01e5e231 $ tail -1 /etc/schroot/default/fstab /dev/disk/by-uuid/dbc64c37-340a-49e5-8184-a69e01e5e231 /mnt/dbc64c37-340a-49e5-8184-a69e01e5e231 none rw,bind 0 0 $ schroot -c sid (sid64)$ ls -al /dev/disk/by-uuid/dbc64c37-340a-49e5-8184-a69e01e5e231 lrwxrwxrwx 1 root root 10 Jan 8 01:00 /dev/disk/by-uuid/dbc64c37-340a-49e5-8184-a69e01e5e231 -> ../../sda1 as well as: $ tail -1 /etc/schroot/default/fstab /mnt/dbc64c37-340a-49e5-8184-a69e01e5e231 /mnt/dbc64c37-340a-49e5-8184-a69e01e5e231 none rw,bind 0 0 Both did not work for me. --- I also tried a naive: $ sudo mount --rbind /mnt/dbc64c37-340a-49e5-8184-a69e01e5e231 /home/malat/schroots/sid-root/mnt/dbc64c37-340a-49e5-8184-a69e01e5e231 $ mount | grep dbc64c37 /dev/sda1 on /mnt/dbc64c37-340a-49e5-8184-a69e01e5e231 type ext4 (rw,nosuid,nodev,relatime,x-gvfs-show) /dev/sda1 on /home/malat/schroots/sid-root/mnt/dbc64c37-340a-49e5-8184-a69e01e5e231 type ext4 (rw,nosuid,nodev,relatime) $ schroot -c sid (sid64)$ ls -al /mnt/dbc64c37-340a-49e5-8184-a69e01e5e231 -> empty !

How can I SSH into a schroot environment using ssh sshuser@192.168.1.20 rather than schroot -c test as user sshuser ? I have read an array of web post on creating a jailed chroot then setting up SSH to limit the user to the jail. I'm trying to set up a schroot environment following this link: https://wiki.debian.org/Schroot

Due to legacy (aka corporate) reasons, I have a number of servers running recent Debian versions (Debian 9, Debian 10) that also need to run older services such as MySQL 5.5. This is done via a (pre-existing) Debian Jessie `schroot` (that was built [using this guide](https://help.ubuntu.com/community/DebootstrapChroot) ) that has the services installed and copies the users from the host. However, I have not been able to find a simple, _trustable_ means to have the services living within that schroot to start at boot time when the schroot is from a user ie.: the schroot is run by one of its root-users, not necessarily by `root`. We have a script to start the schroot:

#at /usr/local/bin/start-legacy.sh
schroot -b -c legacy_schroot -u root -n Session

(this can be run by the schroot's root-user user) And a crontab to invoke at boot time:

#at the root-user user's crontab -e
@reboot /usr/local/bin/start-legacy.sh

However I can't seem to find a means to pass commands to this schroot session at boot time, so as to have it start the services. The following things all don't work: 1.- Pass the commands immediately during the startup script:

#at /usr/local/bin/start-legacy.sh
schroot -b -c legacy_schroot -u root -n Session
schroot -r Session -u root -- service mysql start

When done this way, it works perfectly when a user logins and runs the script manually, but when running from a crontab it only starts the session and doesn't pass the following commands. It doesn't seem to report an error either, or if it does I can't find it. 2a.- Adding the startup to the crontab

#at crontab -e
@reboot /usr/local/bin/start-legacy.sh
@reboot sleep 10 && bash -l -c 'schroot -r -c Session -u root -- service mysql start'

If I do this at crontab, the same effect as above: the script is started OK, but the startup commands are never passed. 2b.- Adding the startup scripts to a command at crontab

#at crontab -e
@reboot /usr/local/bin/start-legacy.sh
@reboot sleep 10 && bash -l -c '/usr/local/bin/start-legacy-mysql.sh'

(where the second script has the `schroot -r` command) Same difference. 3.- Using `/etc/rc.local`

#at /etc/rc.local
su usuario -l -c '/usr/local/bin/start-legacy.sh'
su usuario -l -c '/usr/local/bin/start-legacy-mysql.sh'

exit 0

This _only_ works without the 'su', making the schroot session be started by root; but I need to run the session as the normal user so users can connect to the schroot afterwards. _With_ the su, it's giving a "Not Authorized" error that I can't fetch because I can't find the boot logs except for dmesg's and the screen clears during the boot. Even if it worked, this requires root to setup, which the crontab solution doesn't. I personally don't mind, but I don't think the bosses will want to give root access to the technicians whose only task is to deal with MySQL to set this up. tl;dr: I want to have during boot a number of commands to be run on behalf of a user to perform various tasks on a schroot of which the given user is root.

my host system is archlinux and i need an ubuntu enviornment ready to be used with the files in my home directory. Problem is: my home directory is encrypted using ecryptfs. So when i launch the schroot this is what i get: ~ $ schroot -c ubuntu-lts (ubuntu-lts) ~ $ ls Access-Your-Private-Data.desktop README.txt How can i automount my encrypted home directory (possibly without re-entering my password). To setup my encrypted home on archlinux i have followed this: - https://wiki.archlinux.org/index.php/ECryptfs#Encrypting_a_home_directory - https://wiki.archlinux.org/index.php/ECryptfs#Auto-mounting My schroot setup is very simple: ~ $ cat /etc/schroot/chroot.d/ubuntu-lts.conf [ubuntu-lts] type=directory description=Ubuntu 18.04 LTS directory=/opt/schroot/ubuntu-lts users= aliases=ubuntu-18.04,ubuntu-bionic,bionic

I have a Debian 9 installation with a Debian 6 chroot jail. I am using a proprietary application which up until recently worked fine in the jail. But when I run its newer versions, it crashes in libc. I tired creating a newer Debian jail (Debian 8) but it still crashes. If I run it on native Debian 8, it works. If I import my Debian 6/8 jail in Docker, it still works. Does anybody have any idea why the application would crash in chroot but not when running naively or when the chroot directory is imported and ran in Docker?

I'm trying to configure a file chroot, following the "man" documentation. According to the manpage of schroot, I can use a filesystem tree archive file, and the configure an schroot to use that archive as file system. For example, in /etc/schroot.conf, the following example exists: #[lenny-file] #description=Debian lenny (oldstable) #file=/srv/chroot/lenny.tar.gz #location=/lenny #groups=sbuild So I changed it a little to: [stretch-file] description=Debian Stretch file=/tmp/jail.tar location=/jail groups=sbuild Of course, /tmp/jail.tar exists, and contains minimal bootsrapped stretch. When trying to enter the chroot with schroot -c chroot:stretch-file I get the following warning: W: line 77 [stretch-file]: Obsolete key ‘location’ used I: This option has been removed, and no longer has any effect W: line 76 [stretch-file] file: Configuration key name ‘file’ is not a permitted name. I thing that the interesting line is Configuration key name ‘file’ is not a permitted name. - How can it be? Is the man page wrong? Or do I do anything in the wrong way?

### What am I trying to do? I'm writing a code evaluator using chroot and python and went to hackerrank for some inspiration. ### What I think is happening at Hackerrank? Hackerrank creates run-XXXXXXXXXXXXXXXXXXXX folder for every run of a user program submission, each of these folders has a unique owner and only it's owner has read/write access to it. This means that a particular user 15307 cannot read/modify the contents of the other folders present. ### Coming to the question How would someone go about implementing this using chroot and python or any other language for that matter? Is it creating a user everytime? #### Output of ls -al total 140 drwxrwx--x 2 15307 15307 4096 Jun 24 19:17 . drwxr-xr-x 68 root 0 118784 Jun 24 19:17 .. -rw-r--r-- 1 15307 15307 0 Jun 24 19:17 compile.err -rw-rw---- 1 15307 15307 0 Jun 24 19:17 error00000.err -rw-r----- 1 15307 15307 27 Jun 24 19:17 input00000.in -rw-rw---- 1 15307 15307 0 Jun 24 19:17 output00000.out -rwxrwx--- 1 root 0 783 Jun 24 19:17 request.json -rw-rw---- 1 15307 15307 52 Jun 24 19:17 solution.py -rw-r--r-- 1 15307 15307 213 Jun 24 19:17 solution.pyc #### Output of ls -al / total 504 drwxr-xr-x 68 root 0 118784 Jun 24 19:17 . drwxr-xr-x 68 root 0 118784 Jun 24 19:17 .. drwxr-xr-x 3 ubuntu 0 4096 Jan 25 11:41 android drwxr-xr-x 2 root 0 4096 Apr 9 06:30 bin drwxrwx--x 2 17450 17450 4096 Jun 24 19:08 custom-H8tFpKOEWGsc0s6lvpRk drwxrwx--x 2 14667 14667 4096 Jun 24 19:15 custom-QiOC2dqgU3pVUlFU4ZWz drwxr-xr-x 13 root 0 3860 Jun 24 19:08 dev drwxr-xr-x 10 root 0 4096 May 6 05:37 etc drwxrwx--x 2 18227 18227 4096 Jun 24 19:13 game-player1-YeDYLpA2uIqJFeZ3d97T9IuRAKoqDhyM drwxr-xr-x 4 root 0 4096 May 6 05:37 home drwxr-xr-x 21 root 0 4096 Jun 21 06:36 lib drwxr-xr-x 2 root 0 4096 Jun 21 06:36 lib32 drwxr-xr-x 2 root 0 4096 Jun 21 06:36 lib64 drwx------ 2 root 0 16384 Jan 25 09:18 lost+found drwxr-xr-x 5 root 0 4096 Jan 25 14:10 opt dr-xr-xr-x 127 root 0 0 Jun 24 19:08 proc drwxr-xr-x 7 root 0 4096 Jun 21 10:30 root drwxr-xr-x 22 root 0 800 Jun 24 19:08 run drwxrwx--x 2 15307 15307 4096 Jun 24 19:17 run-1KpGsxE8tJkf4JZhNa3O drwxrwx--x 2 19186 19186 4096 Jun 24 19:12 run-1a89kLrOIvxSKmcG8Vxf drwxr-x--- 2 root 0 4096 Jun 24 19:13 run-1tPF28PnLjSHnwiPQQKw drwxrwx--x 2 18229 18229 4096 Jun 24 19:12 run-1z3LUuz9SddZHYtT6DXl drwxrwx--x 2 17407 17407 4096 Jun 24 19:14 run-2KfLhB5KQJ9hFnT32apd drwxrwx--x 2 13423 13423 4096 Jun 24 19:15 run-2kNHf7UsoOBjeQI2Tcbk drwxrwx--x 2 13477 13477 4096 Jun 24 19:12 run-6fuBJP7ZgZfEm2k9vkZV drwxrwx--x 2 14824 14824 4096 Jun 24 19:08 run-8MlwJE1ia8bR86MbVYi8 drwxrwx--x 2 15984 15984 4096 Jun 24 19:13 run-A3YDoqR2J9cGAhILYDqZ drwxrwx--x 2 16989 16989 4096 Jun 24 19:16 run-AQQjyqXYSXeFZ9wzI5dy drwxrwx--x 2 18819 18819 4096 Jun 24 19:15 run-AvAUgIkcFtieewAFZ6dZ drwxrwx--x 2 13189 13189 4096 Jun 24 19:14 run-FldwZMBI51tvTI3bzTqf drwxrwx--x 2 15862 15862 4096 Jun 24 19:08 run-GORpHssv6tp0WFktcKlE drwxrwx--x 3 15041 15041 4096 Jun 24 19:14 run-GmRpaAqK23cjuC3opP6G drwxrwx--x 2 12977 12977 4096 Jun 24 19:12 run-zlriB5scmjE0ASSjie2r drwxr-xr-x 2 root 0 4096 Jun 21 06:37 sbin drwx------ 3 root 0 4096 Jun 24 19:08 store drwxrwxrwt 4 root 0 4096 Jun 24 19:17 tmp drwxr-xr-x 14 root 0 4096 Jan 25 11:36 usr drwxr-xr-x 6 root 0 4096 May 2 16:53 var

E.g. there are schroot configs: 1: [release-8.i386] personality=linux32 description=TSS version 8 on Debian Wheezy i386 directory=/chroot/release/8.i386 type=directory users=release,balage 2: [release-7.i386] personality=linux32 description=TSS version 7 on Debian Wheezy i386 directory=/chroot/release/7.i386 type=directory users=release,balage It can be see, a template file could be used well: [release-${VERSION}.${ARCH}] personality=linux32 description=TSS version ${VERSION} on Debian Wheezy ${ARCH} directory=/chroot/release/${VERSION}.${ARCH} type=directory users=release,balage Is it possible to create such template config file and to use it in a schroot config file?

I have more schroots but there are a base part which is the same in the all schroot configs (like users, type, etc.). Can be this base file used/sourced in a schroot config file to avoid copying?

I am running Ubuntu 14.04.2, 64 bit host system. Using debootstrap, I installed a minimal Ubuntu 14.04.2, 32 bit system in trusty32 directory. This is what my schroot configuration look like: [trusty_i386] description=Ubuntu 14.04 Trusty for i386 directory=/home/dipanjan/trusty32 personality=linux32 root-users=dipanjan type=directory users=dipanjan I logged in to the 32-bit jail once using chroot, next time using schroot. Astonishingly, the output of uname -m differs. In chroot session, x86_64 (host system architecture) is returned while in schroot session, i686 (guest system architecture) is returned. Can someone explain this discrepancy? $ sudo chroot trusty32/ (trusty_i386)root@dipanjan-OptiPlex-960:/# uname -m x86_64 (trusty_i386)root@dipanjan-OptiPlex-960:/# exit exit $ schroot -c trusty_i386 (trusty_i386)dipanjan@dipanjan-OptiPlex-960:~$ uname -m i686 (trusty_i386)dipanjan@dipanjan-OptiPlex-960:~$ exit logout

I am trying to package an Ubuntu package as a Debian package. For maintainability I am trying to use sbuild. Following the steps here I go through the first five steps, but when I try to build I get chroot errors. These are the steps: 1 sudo apt-get install sbuild 2 sudo mkdir /root/.gnupg # To work around #792100 3 sudo sbuild-update --keygen 4 sudo sbuild-adduser $LOGNAME 5 ... *logout* and *re-login* or use newgrp sbuild in your current shell 6 sudo sbuild-createchroot --make-sbuild-tarball=/srv/chroot/unstable-amd64.tar.gz unstable mktemp -d http://httpredir.debian.org/debian The sbuild-createchrrot command that I use is: CODE: SELECT ALL sudo sbuild-createchroot --make-sbuild-tarball=/srv/chroot/jessie-amd64.tar.gz jessie mktemp -d http://httpredir.debian.org/debian I: SUITE: jessie I: TARGET: /tmp/tmp.uLbQox2R0X I: MIRROR: http://httpredir.debian.org/debian I: Running debootstrap --arch=amd64 --variant=buildd --verbose --include=fakeroot,build-essential,debfoster --components=main --resolve-deps jessie /tmp/tmp.uLbQox2R0X http://httpredir.debian.org/debian I: Retrieving Release I: Retrieving Release.gpg I: Checking Release signature I: Valid Release signature (key id 75DDC3C4A499F1A18CB5F3C8CBF8D6FD518E17E1) I: Retrieving Packages I: Validating Packages I: Resolving dependencies of required packages... I: Resolving dependencies of base packages... I: Found additional required dependencies: acl adduser dmsetup insserv libaudit-common libaudit1 libbz2-1.0 libcap2 libcap2-bin libcryptsetup4 libdb5.3 libdebconfclient0 libdevmapper1.02.1 libgcrypt20 libgpg-error0 libkmod2 libncursesw5 libprocps3 libsemanage-common libsemanage1 libslang2 libsystemd0 libudev1 libustr-1.0-1 procps systemd systemd-sysv udev I: Found additional base dependencies: binutils bzip2 cpp cpp-4.9 debian-archive-keyring dpkg-dev g++ g++-4.9 gcc gcc-4.9 gnupg gpgv libapt-pkg4.12 libasan1 libatomic1 libc-dev-bin libc6-dev libcilkrts5 libcloog-isl4 libdpkg-perl libfakeroot libgc1c2 libgcc-4.9-dev libgdbm3 libgmp10 libgomp1 libisl10 libitm1 liblsan0 libmpc3 libmpfr4 libquadmath0 libreadline6 libstdc++-4.9-dev libstdc++6 libtimedate-perl libtsan0 libubsan0 libusb-0.1-4 linux-libc-dev make patch perl perl-modules readline-common xz-utils I: Checking component main on http://httpredir.debian.org/debian ... I: Retrieving acl 2.2.52-2 I: Validating acl 2.2.52-2 I: Retrieving libacl1 2.2.52-2 I: Validating libacl1 2.2.52-2 I: Retrieving adduser 3.113+nmu3 I: Validating adduser 3.113+nmu3 I: Retrieving apt 1.0.9.8.2 I: Validating apt 1.0.9.8.2 I: Retrieving libapt-pkg4.12 1.0. It continues until it finishes, I am not sure if these are errors, but this happens right before I regain control over the terminal. I: Base system installed successfully. I: Configured /etc/hosts: ┌──────────────────────────────────────────────────────────────────────── │127.0.0.1 hn localhost └──────────────────────────────────────────────────────────────────────── I: Configured /usr/sbin/policy-rc.d: ┌──────────────────────────────────────────────────────────────────────── │#!/bin/sh │echo "All runlevel operations denied by policy" >&2 │exit 101 └──────────────────────────────────────────────────────────────────────── I: Configured APT /etc/apt/sources.list: ┌──────────────────────────────────────────────────────────────────────── │deb http://httpredir.debian.org/debian jessie main │deb-src http://httpredir.debian.org/debian jessie main └──────────────────────────────────────────────────────────────────────── I: Please add any additional APT sources to /tmp/tmp.uLbQox2R0X/etc/apt/sources.list I: Setting reference package list. I: Updating chroot. Ign http://httpredir.debian.org jessie InRelease Hit http://httpredir.debian.org jessie Release.gpg Hit http://httpredir.debian.org jessie Release Get:1 http://httpredir.debian.org jessie/main Sources [7058 kB] Get:2 http://httpredir.debian.org jessie/main amd64 Packages [6763 kB] Get:3 http://httpredir.debian.org jessie/main Translation-en [4582 kB] Fetched 18.4 MB in 21s (837 kB/s) Reading package lists... Done Reading package lists... Done Building dependency tree... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. I: chroot /tmp/tmp.uLbQox2R0X has been removed. I: Successfully set up jessie chroot. I: Run "sbuild-adduser" to add new sbuild users. After that I try to run: sbuild -d jessie filename.dsc Then I get this error: ╔══════════════════════════════════════════════════════════════════════════════╗ ║ simplescreenrecorder 0.3.6+1~ppa1~wily1 (amd64) 07 Feb 2016 04:15 ║ ╚══════════════════════════════════════════════════════════════════════════════╝ Package: simplescreenrecorder Version: 0.3.6+1~ppa1~wily1 Source Version: 0.3.6+1~ppa1~wily1 Distribution: jessie Machine Architecture: amd64 Host Architecture: amd64 Build Architecture: amd64 E: /etc/schroot/schroot.conf: Failed to stat file: No such file or directory ┌──────────────────────────────────────────────────────────────────────────────┐ │ Summary │ └──────────────────────────────────────────────────────────────────────────────┘ Then the cursor just sits there blinking. What is wrong with the chroot? How come sbuild isn't setting it up properly? How do I fix this to use sbuild? sbuild: Installed: 0.65.2-1 Candidate: 0.65.2-1 Version table: 0.66.0-5~bpo8+1 0 100 http://httpredir.debian.org/debian/ jessie-backports/main amd64 Packages *** 0.65.2-1 0 500 http://httpredir.debian.org/debian/ jessie/main amd64 Packages 100 /var/lib/dpkg/status schroot: Installed: 1.6.10-1+b1 Candidate: 1.6.10-1+b1 Version table: *** 1.6.10-1+b1 0 500 http://httpredir.debian.org/debian/ jessie/main amd64 Packages 100 /var/lib/dpkg/status **Edit:** I do not have the below file or folders nor do I really know how to manually create them. The wiki didn't really say much about these files. E: /etc/schroot/schroot.conf: Failed to stat file: No such file or directory **edit** this is the contents of my /etc/schroot folder tree /etc/schroot/ /etc/schroot/ ├── buildd ├── chroot.d │   └── jessie-amd64-sbuild-k92zq_ ├── default ├── desktop ├── minimal ├── sbuild └── setup.d └── 99check -> 00check 7 directories, 2 files this is the content of that jessie-amd64 file cat /etc/schroot/chroot.d/jessie-amd64-sbuild-k92zq_ [jessie-amd64-sbuild] type=file description=Debian jessie/amd64 autobuilder file=/srv/chroot/jessie-amd64.tar.gz groups=root,sbuild root-groups=root,sbuild profile=sbuild when I run schroot -c jessie-amd64-sbuild E: /etc/schroot/schroot.conf: Failed to stat file: No such file or directory schroot -c jessie-amd64 E: /etc/schroot/schroot.conf: Failed to stat file: No such file or directory They still just give an error even though I am using the -c command, it's complaining about the schroot.conf file. I've tried to write this to the schroot.conf file cat /etc/schroot/schroot.conf [jessie-amd64] type=file description=Debian jessie/amd64 autobuilder file=/srv/chroot/jessie-amd64.tar.gz groups=root,sbuild root-groups=root,sbuild profile=sbuild then tried to run schroot -c /etc/schroot/schroot.conf schroot -c jessie-amd64 E: /srv/chroot/jessie-amd64.tar.gz: Failed to stat file: No such file or directory then I get the above error.

I'm using schroot with aufs. Currently, my conf file under \etc\schroot\chroot.d looks like [trusty_chrome] description=Ubuntu 14.04 Trusty running Chrome and Adobe Flash directory=/srv/chroot/trusty_chrome personality=linux ... union-type=aufs union-mount-options=br:/srv/chroot/trusty_chrome.aufs=rw:/srv/chroot/base/trusty_amd64=ro Basically, the overlay and underlay directory is specified in the mount option. While man schroot.conf hints that they could also be determined by keys union-overlay-directory and union-underlay-directory, while I can not enter chroot properly with these options. More precisely, if I use the following conf, [trusty_chrome] description=Ubuntu 14.04 Trusty running Chrome and Adobe Flash directory=/srv/chroot/trusty_chrome personality=linux ... union-type=aufs union-overlay-directory=/srv/chroot/trusty_chrome.aufs union-underlay-directory=/srv/chroot/base/trusty_amd64 I'll encounter errors E: 20copyfiles: cp: cannot create regular file '/var/lib/schroot/mount/trusty_chrome-cb1db93d-c07c-4c2d-bef2-f5025358c2b3/etc/resolv.conf': No such file or directory E: trusty_chrome-cb1db93d-c07c-4c2d-bef2-f5025358c2b3: Chroot setup failed: stage=setup-start when try to enter this chroot. So the question is, how could I configure schroot using aufs by keys union-overlay-directory and union-underlay-directory. Moreover, when I list all chroot managed $ schroot -l chroot:trusty_chrome ... source:trusty_chrome ... I'll find two entries for each chroot using aufs. Is source:blabla a chroot? I can't enter them by schroot. I'm using schroot (Debian sbuild) 1.6.10 (04 May 2014) in Ubuntu 14.10.

I have a wheezy chroot running on squeeze, using schroot. I'm successfully using Skype. I've installed google-chrome-stable_current_i386.deb (version 38) in the chroot but when I try to run it, it exits immediately and says Aborted. I ran it with strace which indicates this is because it received SIG_ABORT. When I run google-chrome-stable --disable-setuid-sandbox it works, but complains about stability and security. (Obviously it's using a sandbox for a reason.) I suspect I'm having the same issue as [How do I run chromium inside a chroot?](https://unix.stackexchange.com/questions/94423/how-do-i-run-chromium-inside-a-chroot) .

When I had to repair my Debian system, I tried to use schroot due the convenience of not having to mount bind several partitions. But, contrary to my expectations, schroot decided to override my passwd file and other configuration files (in /etc and my home directory) which I didn't like (and sometimes causes [weird messages](https://unix.stackexchange.com/questions/160486/error-message-unknown-user-geoclue-in-statoverride-file)) . Is there a way to prevent that behavior? I used the type directory for schroot, since it seemed the one I needed. I checked the man page and only found a --preserve-environment option, but from its description I'm not sure if it preserves the chrooted system environment or just copies my user environment to the chroot session instead of a clean slate (which is the default).

I obtained a strange error message inside a chroot: unknown user 'geoclue' in statoverride file when running apt-get install or apt-get upgrade. I use schroot to enter this chroot. I found that I had a package called geoclue-2.0 installed in the chroot, and I purged it. apt-get purge geoclue-2.0 This made the problem go away. What caused this problem? I'm running Debian wheezy on the host machine. The chroot is running Debian jessie (testing). I asked about this on chat, and this prompted Braiam to post the closely related [How to prevent schroot from overridding passwd file and others files already present on the chrooted system?](https://unix.stackexchange.com/q/160487/4671)