running-in-container exits 1 as non-root even inside a container
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| upstart (Ubuntu) |
Confirmed
|
Low
|
Unassigned | ||
Bug Description
$ sudo running-
lxc
$ running-
1
it should at very least exit with something other than '1' this canont be determined other than as root.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: upstart 1.4-0ubuntu8
ProcVersionSign
Uname: Linux 3.2.0-17-virtual x86_64
ApportVersion: 1.93-0ubuntu2
Architecture: amd64
Date: Tue Feb 28 23:17:20 2012
Ec2AMI: ami-00000000
Ec2AMIManifest: FIXME
Ec2Availability
Ec2InstanceType: m1.small
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
ProcEnviron:
TERM=screen
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: upstart
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile.
| Scott Moser (smoser) wrote | #1 |
| Serge Hallyn (serge-hallyn) wrote | #2 |
| Changed in upstart (Ubuntu): | |
| status: | New → Confirmed |
| importance: | Undecided → Low |
| Serge Hallyn (serge-hallyn) wrote | #3 |
Thanks for submitting this bug.
I'm not sure what we should do about this.
1. we could install dbus in all containers. dbus is required in order for non-root tasks to talk to upstart.
2. we could have running-
or we could do nothing, and say it's workign as designed.
I'm tempted to say let's do (2), but I have a feeling we'll keep running into other problems if we don't do (1).