Github messages for voidlinux
 help / color / mirror / Atom feed
From: TegarOk <TegarOk@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Cant start container, suspect its because LXD 4.19
Date: Sun, 29 May 2022 11:26:26 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37340@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1268 bytes --]

New issue by TegarOk on void-packages repository

https://github.com/void-linux/void-packages/issues/37340

Description:
<!-- Don't request update of package. We have a script for that. https://repo-default.voidlinux.org/void-updates/void-updates.txt. However, a quality pull request may help. -->
### System
CPU: Ryzen 7 1700
GPU: HD 7870
* xuname:  
Void 5.10.117_1 x86_64 AuthenticAMD notuptodate rrmDFFFF (I've updated yesterday).
* package:  
(Sorry i just remove it and moved to lxd-lts instead the latest one from repository, but the LXD version is the latest from main repository, 4.19 if i not wrong).
### Expected behavior
Container should be start.
### Actual behavior
Container cant start because of Error (See https://github.com/lxc/lxd/issues/9419, the problem is similar)
### Steps to reproduce the behavior

1. Download & install LXD from repository.
2. Start the service.
3. Running 'lxd init'
4. Try launch & start container.
5. Got Error.

Forgot to save the log, but the error & log is similar to https://github.com/lxc/lxd/issues/9419.

For someone who having this problem too, switch to 'lxd-lts' for now. Its running without a problem, but you need to start new container because lxd just complain it if you are downgrade.

             reply	other threads:[~2022-05-29  9:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-29  9:26 TegarOk [this message]
2022-06-01 21:55 ` CameronNemo
2022-06-07 16:16 ` TegarOk
2022-06-07 16:16 ` [ISSUE] [CLOSED] " TegarOk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37340@inbox.vuxu.org \
    --to=tegarok@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).