schroot sudo main: unable to allocate memory

Bug #1647832 reported by Noah Delatoba
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
sudo (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Unable to use sudo within zesty armhf chroot on trusty arch64. Getting error unable to to allocate memory.

$ sudo ls
sudo: main: unable to allocate memory

kernel - 4.4.0-38-generic
release - Ubuntu 14.04.5 LTS
system architecture - arm64
chroot architecture - armhf

sudo:
  Installed: 1.8.9p5-1ubuntu1.3
  Candidate: 1.8.9p5-1ubuntu1.3
  Version table:
 *** 1.8.9p5-1ubuntu1.3 0
        500 http://ports.ubuntu.com/ubuntu-ports/ trusty-updates/main arm64 Packages
        100 /var/lib/dpkg/status
     1.8.9p5-1ubuntu1.1 0
        500 http://ports.ubuntu.com/ubuntu-ports/ trusty-security/main arm64 Packages
     1.8.9p5-1ubuntu1 0
        500 http://ports.ubuntu.com/ubuntu-ports/ trusty/main arm64 Packages

Revision history for this message
Brian Murray (brian-murray) wrote :

I was unable to recreate this on an amd64 chroot:

 $ schroot -u bdmurray -c zesty-amd64
W: Shell ‘/bin/zsh’ not available: /bin/zsh: Failed to stat file: No such file or directory
W: Falling back to shell ‘/bin/bash’
(zesty-amd64)bdmurray@impulse:~/source-trees/ubuntu-archive-tools/phased-update-overrides$ sudo apt-get install 2vcard
[sudo] password for bdmurray:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  2vcard
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 13.0 kB of archives.
After this operation, 53.2 kB of additional disk space will be used.
Get:1 http://192.168.10.7/ubuntu zesty/universe amd64 2vcard all 0.6-1 [13.0 kB]
Fetched 13.0 kB in 0s (438 kB/s)
Selecting previously unselected package 2vcard.
(Reading database ... 13744 files and directories currently installed.)
Preparing to unpack .../archives/2vcard_0.6-1_all.deb ...
Unpacking 2vcard (0.6-1) ...
Setting up 2vcard (0.6-1) ...

Revision history for this message
Brian Murray (brian-murray) wrote :

Actually that was a terrible test, ignore that comment.

Revision history for this message
Adam Conrad (adconrad) wrote :

Closing as invalid, sudo was having a sad due to a lack of virtual filesystems being mounted in the chroot.

Changed in sudo (Ubuntu):
status: New → Invalid
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.