On Ubuntu 16.04..2 LTS, kernel 4.4.0-78-generi
inside a container I erase the file /etc/mtab
the containers start, a new file /etc/mtab gets created
I stop the container,
I start the container
the line with tmpfs starts growing ad -infinitum, this way
tmpfs /run/shm tmpfs
rw,noexec,nosuid,nodev,s
On Thu, May 18, 2017 at 11:06 PM, Saint Michael wrote:
> On Ubuntu 16.04..2 LTS, kernel 4.4.0-78-generi
>
> inside a container I erase the file /etc/mtab
>
why?
> the containers start, a new file /etc/mtab gets created
>
Is it a regular file or a symlink? IIRC on ubuntu /etc/mtab is symlink
I guess it wouldn't hurt to elaborate
On Ubuntu 16.04..2 LTS, kernel 4.4.0-78-generic
- is that you host OS?
- what's the lxc/lxd version you are running
- which container are you running (I mean created from which image)?
On 5/19/2017 12:06 AM, Saint Michael wrote:
On Ubuntu 16.04..2 LTS,
In my debian container, it is file.
It gets recreated all the time I reboot.
what am I doing wrong?
This is the config file
lxc.mount.entry = proc proc proc nodev,noexec,nosuid 0 0
lxc.mount.entry = sysfs sys sysfs defaults 0 0
lxc.tty = 4
lxc.pts = 1024
lxc.cgroup.devices.deny = a
lxc.cgroup.devi
The host is Ubuntu 16.04.2 LTS, the container is Debian GNU/Linux 7
On Thu, May 18, 2017 at 8:13 PM, Saint Michael wrote:
> In my debian container, it is file.
> It gets recreated all the time I reboot.
> what am I doing wrong?
> This is the config file
> lxc.mount.entry = proc proc proc nodev,
On Fri, May 19, 2017 at 7:16 AM, Saint Michael wrote:
> The host is Ubuntu 16.04.2 LTS, the container is Debian GNU/Linux 7
>
>
> On Thu, May 18, 2017 at 8:13 PM, Saint Michael wrote:
>
>> In my debian container, it is file.
>> It gets recreated all the time I reboot.
>>
>
What happens when you
a bit OT related to this thread but from what Fajar has posted here it
almost sounds like you shouldn't/couldn't use debian inside a container
unless you are prepared to conduct far from trivial post launch system
tweaking (reinstalling systemd was mentioned)
Is that a valid assumption?
On
On Fri, May 19, 2017 at 7:45 AM, gunnar.wagner
wrote:
> a bit OT related to this thread but from what Fajar has posted here it
> almost sounds like you shouldn't/couldn't use debian inside a container
> unless you are prepared to conduct far from trivial post launch system
> tweaking (reinstallin
The container is Debian 7. It does not use systemd.
On Thu, May 18, 2017 at 9:01 PM, Fajar A. Nugraha wrote:
> On Fri, May 19, 2017 at 7:45 AM, gunnar.wagner <
> gunnar.wag...@netcologne.de> wrote:
>
>> a bit OT related to this thread but from what Fajar has posted here it
>> almost sounds like
On Fri, May 19, 2017 at 9:12 AM, Saint Michael wrote:
> The container is Debian 7. It does not use systemd.
>
>
Yes. I was using systemd-jessie-unpriv-container case as an example for
'customization required'.
In your case, it should be as simple as:
- use template (or to be more specific, use D
10 matches
Mail list logo
