[Expired for lxc (Ubuntu) because there has been no activity for 60
days.]
** Changed in: lxc (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1470580
[Expired for lxc (Ubuntu) because there has been no activity for 60
days.]
** Changed in: lxc (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
So was this bug just about you reaching the quota and LXC failing then?
Just checking whether there's an actual bug we need to fix ASAP or if
it's just about better error handling.
** Changed in: lxc (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because
So was this bug just about you reaching the quota and LXC failing then?
Just checking whether there's an actual bug we need to fix ASAP or if
it's just about better error handling.
** Changed in: lxc (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because
Quoting god (1470...@bugs.launchpad.net):
Thanks for clarification! Would be kinda helpful if lxc-start could
print actual numbers (X quota configured for bridge123, Y is in use).
Agreed, this would be a huge improvement. Would you like to re-title
this bug to turn it into a feature request
Quoting god (1470...@bugs.launchpad.net):
Thanks for clarification! Would be kinda helpful if lxc-start could
print actual numbers (X quota configured for bridge123, Y is in use).
Agreed, this would be a huge improvement. Would you like to re-title
this bug to turn it into a feature request
Thanks for clarification! Would be kinda helpful if lxc-start could
print actual numbers (X quota configured for bridge123, Y is in use).
What's the upper limit on those quota numbers? Can I have 100 bridges
with 400 interfaces in each?
--
You received this bug notification because you are a
Thanks for clarification! Would be kinda helpful if lxc-start could
print actual numbers (X quota configured for bridge123, Y is in use).
What's the upper limit on those quota numbers? Can I have 100 bridges
with 400 interfaces in each?
--
You received this bug notification because you are a
cat /etc/lxc/lxc-usernet
# USERNAME TYPE BRIDGE COUNT
x veth ibr1 8
x veth xbr1 8
x veth ubr1 8
cat .local/share/lxc/asterisk/config
# Template used to create this
Also, what does Quota reached. mean? What kind of quota is that?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1470580
Title:
unprivileged lxc containers fails with custom bridge
To
cat /etc/lxc/lxc-usernet
# USERNAME TYPE BRIDGE COUNT
x veth ibr1 8
x veth xbr1 8
x veth ubr1 8
cat .local/share/lxc/asterisk/config
# Template used to create this
Btw, is there a way to make logging to actually work and log everything?
Maybe add --logging-indeed-log or smth like that in addition to existing -l and
--logfile?
** Changed in: lxc (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member
Also, what does Quota reached. mean? What kind of quota is that?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1470580
Title:
unprivileged lxc containers fails with custom bridge
To manage
Btw, is there a way to make logging to actually work and log everything?
Maybe add --logging-indeed-log or smth like that in addition to existing -l and
--logfile?
** Changed in: lxc (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member
lxc-start -n asterisk -F
Quota reached.
lxc-start: start.c: lxc_spawn: 1000 failed to create configured network
lxc-start: start.c: __lxc_start: 1164 failed to spawn 'asterisk'
lxc-start: start.c: main: 344 The container failed to start.
lxc-start: start.c: main 348 Additional information can be
lxc-start -n asterisk -F
Quota reached.
lxc-start: start.c: lxc_spawn: 1000 failed to create configured network
lxc-start: start.c: __lxc_start: 1164 failed to spawn 'asterisk'
lxc-start: start.c: main: 344 The container failed to start.
lxc-start: start.c: main 348 Additional information can be
Quoting god (1470...@bugs.launchpad.net):
Also, what does Quota reached. mean? What kind of quota is that?
The last number in /etc/lxc/lxc-usernic gives the # nics which the user
may connect to the specified bridge. The active connections are listed
in /run/lxc/nics. If Quota Reached is seen
Quoting god (1470...@bugs.launchpad.net):
Also, what does Quota reached. mean? What kind of quota is that?
The last number in /etc/lxc/lxc-usernic gives the # nics which the user
may connect to the specified bridge. The active connections are listed
in /run/lxc/nics. If Quota Reached is seen
Indeed, on every error path lxc_user_nic should print an error message
to stderr, but that doesn't end up in the log. If you simply do
lxc-start -n container_name -F
What do you see? On one failure case I see Quota reached, for
instance.
When I copy/paste your network config excerpt, it does
Indeed, on every error path lxc_user_nic should print an error message
to stderr, but that doesn't end up in the log. If you simply do
lxc-start -n container_name -F
What do you see? On one failure case I see Quota reached, for
instance.
When I copy/paste your network config excerpt, it does
Commenting those 2 lines change nothing - same error. Is there way to
figure out what exactly went wrong while creating network? The log seems
way too brief about it even with debug enabled.
** Changed in: lxc (Ubuntu)
Status: Incomplete = New
--
You received this bug notification
Commenting those 2 lines change nothing - same error. Is there way to
figure out what exactly went wrong while creating network? The log seems
way too brief about it even with debug enabled.
** Changed in: lxc (Ubuntu)
Status: Incomplete = New
--
You received this bug notification
22 matches
Mail list logo
