On 09-05-2020 20:31, gunnar.wagner wrote:
>
>> I was unfortunate to choose my containers name such that LXD thinks one is a
>> snapshot of the
>> other.
> hm. Not sure whether this is the explanation. The volume of a snapshot of
> test04 would be named *test04/second* and not *test04-second*.
On 09-05-2020 23:53, Andrey Repin wrote:
> Greetings, Kees Bakker!
>
>> Ah, I found out what is causing this. I was unfortunate to choose
>> my containers name such that LXD thinks one is a snapshot of the
>> other.
>> Simple test
>> root@rapper:~# lxc init
t@rapper:~# lxc init images:ubuntu/bionic/amd64 -p pool2 test04_first
Creating test04_first
Error: Failed instance creation: Invalid instance name: Name can only contain
alphanumeric and hyphen characters
Now I have to find a trick to mislead LXD so that the containers
can be deleted.
-- Kees
On 07
Hey,
(( I don't have much luck with the latest LXD on Ubuntu 20.04. Here is another
problem. ))
I switched a container from one profile (default) to another.
The default profile has no disk size (but is 10GB, I believe). The new
profile has a disk size of 20GB. Oh, and I have a LVM storage
Hi,
When I want to delete a container I'm getting this error
root@ijssel:~# lxc delete jenkins
Error: Error deleting storage volume: Cannot remove a volume that has snapshots
However, it has no snapshots.
root@ijssel:~# lxc info jenkins
Name: jenkins
Location: ijssel
Remote: unix://
Hey,
With LXD (4.0.1) from snap things are quite different with
respect to mounted file systems. In the past (before snap
was more or less enforced), you could simply go to
/var/lib/lxd/storage-pools and you'd see the LVM containers
being mounted there.
I've installed Ubuntu 20.04 and installed
Hi,
I'm installing a new server with Ubuntu 20.04. Not everything
was going as planned, so I want to redo lxd init.
What is the best method to completely whipe LXD's state, so that
I can redo it from scratch?
(( I was a bit surprised that LXD can now only run from snap, but
I guess that's
. In the captured network packets I see something strange. When the DHCP
sees the DISCOVER it pings the "old" IP address, and it gets an answer from the
container. Well, it shouldn't get an answer.
--
Kees Bakker
pEpkey.asc
Description: application/pgp-keys
_
Hey,
In a container I'm running some Apache/PHP service (in this case LibreNMS).
This service
is causing an annoying error in /var/log/syslog which I get to see in logwatch.
The error
message is triggered by a remount done by phpsessionclean, I think.
Here is a sample of the syslog message
On 26-03-19 17:59, Stéphane Graber wrote:
> On Tue, Mar 26, 2019 at 12:04:17PM +0100, Kees Bakker wrote:
>> Hey,
>>
>> It is not clear to me if and how it is possible to set a capability in
>> the config of a container. What I would like to do is to allow
Hey,
It is not clear to me if and how it is possible to set a capability in
the config of a container. What I would like to do is to allow CAP_MKNOD
in a container.
In the old (?) LXC you would presumably use lxc.cap.keep, but that doesn't
work with LXD 3.x
--
Kees
On 11-09-18 15:13, Kees Bakker wrote:
> Hey,
>
> Every now and then we have one or more containers in state ERROR.
> Is there a clever method to recover from that, other than
> rebooting the LXD server?
>
> Killing the monitor and the forkstart does help. And also a kworker
&
the container, then
> restart the container, that should cause LXD to resize it on startup.
>
> On Wed, Sep 26, 2018 at 09:20:02AM +0200, Kees Bakker wrote:
>> Thanks, that works.
>>
>> Next, how do I change the volume size of an existing container?
>>
>> On 25-09-18 1
t; lxc profile device set default root size 50GB
>
> On Tue, Sep 25, 2018 at 04:11:05PM +0200, Kees Bakker wrote:
>> This is a follow up of https://github.com/lxc/lxd/issues/5069
>> (( Sorry for creating the issue, Stéphane. I thought that "issues"
>> were no
Hey,
In my quest to find out how to change volume sizes I ran into this
error message.
# lxc init ubuntu:bionic testvolsize4
# lxc storage volume set local testvolsize4 size 20GB
Error: not found
# lxc storage volume set local container/testvolsize4 size 20GB
Error: The [size] properties cannot
ith the 10GB default.
And, perhaps related, if I have a container with a bigger volume than 10GB,
then it fails to copy that container. (Copying that container to another LXD
server with BTRFS, succeeds without problem.)
Notice that I'm using LVM storage, on Ubuntu 18.04 with LXD/LXC 3.0.1
-- Kees
On 24-09-1
12:19 0:00 \_ [lxc
monitor] /var/lib/lxd/containers xyz
On 11-09-18 15:13, Kees Bakker wrote:
> Hey,
>
> Every now and then we have one or more containers in state ERROR.
> Is there a clever method to recover from that, other than
> rebooting the LXD server?
>
>
Hey,
Forgive my ignorance, but how would you do that? I have a setup with LVM
and the default volume size is 10G. I wish to increase that default,
what would be the command syntax? Also I want to see the current
default settings, just so I know I'm on the right track.
My pool is called "local".
On 13-09-18 05:57, Fajar A. Nugraha wrote:
> On Wed, Sep 12, 2018 at 9:33 PM, Kees Bakker <mailto:ke...@ghs.com>> wrote:
>
> Hey,
>
> This with a LXD/LXC on a Ubuntu 18.04 server. Storage is done
> with LVM. It was installed as a cluster with just one no
Hey,
This with a LXD/LXC on a Ubuntu 18.04 server. Storage is done
with LVM. It was installed as a cluster with just one node.
It was also added as remote for three other LXD servers (all Ubuntu 16.04
and LXD 2.0.x). These old servers have BTRFS storage.
Suddenly I cannot do any lxc command
On 12-09-18 10:51, Fajar A. Nugraha wrote:
> On Wed, Sep 12, 2018 at 3:14 PM, Kees Bakker <mailto:ke...@ghs.com>> wrote:
>
> On 11-09-18 21:56, Andrey Repin wrote:
> > Greetings, Kees Bakker!
> >
> >> ii lxc-common 2.0.8-0ubuntu1~16
On 11-09-18 21:56, Andrey Repin wrote:
> Greetings, Kees Bakker!
>
>> ii lxc-common 2.0.8-0ubuntu1~16.04.2 amd64 Linux Containers
>> userspace tools (common tools)
>> ii lxcfs 2.0.8-0ubuntu1~16.04.2 amd64 FUSE based
>>
On 11-09-18 16:11, Christian Brauner wrote:
>> Kees Bakker hat am 11. September 2018 um 15:54 geschrieben:
>>
>>
>> On 11-09-18 15:40, Christian Brauner wrote:
>>>> Kees Bakker hat am 11. September 2018 um 15:13 geschrieben:
>>>>
>>>>
On 11-09-18 15:40, Christian Brauner wrote:
>> Kees Bakker hat am 11. September 2018 um 15:13 geschrieben:
>>
>>
>> Hey,
>>
>> Every now and then we have one or more containers in state ERROR.
>> Is there a clever method to recover from that, other than
info gives "error: Monitor is hung"
I'm running Ubuntu 16.04 with BTRFS. The kernel is 4.15.0-33-generic
--
Kees Bakker
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users
temd-networkd,
which (I'm guessing) is doing DHCP client stuff).
Can anyone comment on this DHCP client behavior?
--
Kees Bakker
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users
26 matches
Mail list logo
