Your message dated Sat, 29 Apr 2017 20:20:35 +0200
with message-id <b296b532-94fa-0ae1-a289-8f0616a1f...@debian.org>
and subject line Re: /bin/machinectl: Failed to start a raw image using 
machinectl but was able to start using systemd-nspawn
has caused the Debian Bug report #803053,
regarding /bin/machinectl: Failed to start a raw image using machinectl but was 
able to start using systemd-nspawn
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
803053: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803053
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd-container
Version: 227-2
Severity: normal
File: /bin/machinectl

Dear Maintainer,

   Download the image using machinectl pull-raw image
   machinectl start imagename

   failed - error message from journalctl

   Oct 26 16:53:01 vaidyanath systemd-nspawn[495]: Failed to allocate prober 
for /dev/loop3p1: Operation not permitted
   Oct 26 16:53:01 vaidyanath systemd-nspawn[495]: Failed to mount root 
directory: Operation not permitted
   Oct 26 16:53:01 vaidyanath systemd[1]: 
systemd-nspawn@Fedora\x2dCloud\x2dBase\x2d22\x2d20150521.x86_64.service: Main 
process exited, code=exited, status=1/FAILURE
   Oct 26 16:53:01 vaidyanath systemd[1]: Failed to start Container 
Fedora-Cloud-Base-22-20150521.x86_64.
   Oct 26 16:53:01 vaidyanath systemd[1]: 
systemd-nspawn@Fedora\x2dCloud\x2dBase\x2d22\x2d20150521.x86_64.service: Unit 
entered failed state.
   Oct 26 16:53:01 vaidyanath systemd[1]: 
systemd-nspawn@Fedora\x2dCloud\x2dBase\x2d22\x2d20150521.x86_64.service: Failed 
with result 'exit-code'.
   Oct 26 16:53:01 vaidyanath polkitd(authority=local)[4725]: Unregistered 
Authentication Agent for unix-process:490:2594942 (system bus name :1.158, 
object path /org/free

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd-container depends on:
ii  libblkid1        2.27-3
ii  libbz2-1.0       1.0.6-8
ii  libc6            2.21-0experimental1
ii  libcap2          1:2.24-12
ii  libcurl3-gnutls  7.45.0-1
ii  libgcrypt20      1.6.4-3
ii  liblzma5         5.1.1alpha+20120614-2.1
ii  libseccomp2      2.2.3-2
ii  libselinux1      2.4-2
ii  systemd          227-2
ii  zlib1g           1:1.2.8.dfsg-2+b1

systemd-container recommends no packages.

systemd-container suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Version: 232-22
On Mon, 26 Oct 2015 17:24:18 +0530 vaidy <vaidyanat...@gmail.com> wrote:
> Package: systemd-container
> Version: 227-2
> Severity: normal
> File: /bin/machinectl
> 
> Dear Maintainer,
> 
>    Download the image using machinectl pull-raw image
>    machinectl start imagename
> 
>    failed - error message from journalctl
> 
>    Oct 26 16:53:01 vaidyanath systemd-nspawn[495]: Failed to allocate prober 
> for /dev/loop3p1: Operation not permitted
>    Oct 26 16:53:01 vaidyanath systemd-nspawn[495]: Failed to mount root 
> directory: Operation not permitted
>    Oct 26 16:53:01 vaidyanath systemd[1]: 
> systemd-nspawn@Fedora\x2dCloud\x2dBase\x2d22\x2d20150521.x86_64.service: Main 
> process exited, code=exited, status=1/FAILURE
>    Oct 26 16:53:01 vaidyanath systemd[1]: Failed to start Container 
> Fedora-Cloud-Base-22-20150521.x86_64.
>    Oct 26 16:53:01 vaidyanath systemd[1]: 
> systemd-nspawn@Fedora\x2dCloud\x2dBase\x2d22\x2d20150521.x86_64.service: Unit 
> entered failed state.
>    Oct 26 16:53:01 vaidyanath systemd[1]: 
> systemd-nspawn@Fedora\x2dCloud\x2dBase\x2d22\x2d20150521.x86_64.service: 
> Failed with result 'exit-code'.
>    Oct 26 16:53:01 vaidyanath polkitd(authority=local)[4725]: Unregistered 
> Authentication Agent for unix-process:490:2594942 (system bus name :1.158, 
> object path /org/free

Sorry for not responding earlier.
I just tried this and it seems to work fine with v232 from testing.

I'm thus closing the bug report for this version assuming this issue has
been fixed in the mean time.

Regards,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Reply via email to