Package Details: clean-chroot-manager 2.95-1

Git Clone URL: https://aur.archlinux.org/clean-chroot-manager.git (read-only)
Package Base: clean-chroot-manager
Description: Wrapper scripts for managing clean chroots.
Upstream URL: https://github.com/graysky2/clean-chroot-manager
Licenses: MIT
Conflicts: clean_chroot_manager
Replaces: clean_chroot_manager
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 57
Popularity: 1.756167
First Submitted: 2013-08-18 16:52
Last Updated: 2019-04-13 22:14

Required by (0)

Sources (1)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »

graysky commented on 2015-01-27 12:33

Bump to v2.64-1

Changelog: Fix user detect under tmux and urxvt.
Commit: https://github.com/graysky2/clean-chroot-manager/compare/v2.61...v2.64

graysky commented on 2015-01-24 16:07

Bump to v2.62-1

Changelog: Minor note added to skel.
Commit: https://github.com/graysky2/clean-chroot-manager/compare/v2.61...v2.62

graysky commented on 2015-01-15 21:37

Execute commands in the chroot? This package merely controls the devtools scripts for building in a clean environment... what you want is out of scope. I believe you want a totally separate package for that called schroot. See the wiki. https://wiki.archlinux.org/index.php/Schroot

EDIT: wait, guess we need to define what you wanna do... just doing operations in the clean-chroot can be done as you posted below I believe... if however you wanna have a sandbox in a chroot, and run something from within it, that is what schroot can do.

graysky commented on 2015-01-15 21:35

Execute commands in the chroot? This package merely controls the devtools scripts for building in a clean environment... what you want is out of scope. I believe you want a totally separate package for that called schroot. See the wiki. https://wiki.archlinux.org/index.php/Schroot

ceri commented on 2015-01-15 21:33

@graysky
That works too, but I wanted to figure out how to execute commands in the chroot in any case.

graysky commented on 2015-01-15 20:58

I have a line in /etc/fstab setting up the tmpfs:
tmpfs /scratch tmpfs nodev,size=28G 0 0

And I have systemd create the two dirs for me with /etc/tmpfiles.d/tmpfs_dirs.conf which contains:
d /scratch/.chroot64 0755 facade users -
d /scratch/.chroot32 0755 facade users -

coderkun commented on 2015-01-15 16:27

graysky: How do you set the tmpfs up and make sure that it is built at boot?

graysky commented on 2015-01-15 15:22

Or just nuke and rebuild your chroot.. My system has quite a bit of RAM so I actaully put $CHROOT in tmpfs which is good for several reasons, speed, no wear to my ssd, and it always gets built freshly when I reboot.

ceri commented on 2015-01-15 13:06

To fix the following error (after the major pacman update):

error: failed to initialize alpm library
(database is incorrect version: /var/lib/pacman/)
error: try running pacman-db-upgrade

Run the following:

arch-nspawn $CHROOT/root pacman-db-upgrade

(specify or change $CHROOT to your chroot)

graysky commented on 2015-01-07 14:53

@BeepDog - OK. For tmux to work, it requires a patch from tmux-git. I opened a FS asking for it to be included in the official package[1], but you can try it from the files in the FS yourself or build tmux from git and have libutempter installed before compiling it.

1. https://bugs.archlinux.org/task/43368