nspawn / mkosi-definitions Goto Github PK

View Code? Open in Web Editor NEW

24.0 6.0 5.0 293 KB

This repository contains the mkosi definitions for the images

License: GNU General Public License v3.0

Shell 100.00%

mkosi-definitions's Introduction

mkosi-definitions

This repository contains the mkosi definitions for the images

mkosi-definitions's People

Stargazers

Watchers

Forkers

shibumi edu4rdshl dr460nf1r3 mrc0mmand manuelm

mkosi-definitions's Issues

Couldn't change read-only permissions on XFS

Idk, if this is intentional, and if this is just missing on the homepage or an actual issue.
I just downloaded archlinux-archlinux.tar, and it worked successful until the point, at that it refused to write anything.

Inside the system, it reports it is a read-only filesystem - is this intended to be the case by default?
And outside of the system, I try to launch it via

machinectl read-only archlinux-archlinux-tar false

And get this error message, despite that I am root:
Could not mark image read-only: Access denied

Fedora 37 and 38 are missing

Thanks!

Add a systemd-portabled repo

systemd Portable Services is a great feature that systemd has implemented, currently, we build systemd-nspawn images would be good if we can have a Portabled repo in the future.

Documentation about Portable Services: https://systemd.io/PORTABLE_SERVICES/

RAW zstd-compressed images fails to start

machinectl start image.raw.zstd

Job for [email protected] failed because the control process exited with error code.
See "systemctl status [email protected]" and "journalctl -xeu [email protected]" for details.

systemctl status [email protected]

x [email protected] - Container image.raw.zstd
     Loaded: loaded (/usr/lib/systemd/system/[email protected]; disabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Sun 2022-02-27 13:33:08 CET; 40s ago
       Docs: man:systemd-nspawn(1)
    Process: 6278 ExecStart=systemd-nspawn --quiet --keep-unit --boot --link-journal=try-guest --network-veth -U --settings=override --machine=image.raw.zstd (code=exited, status=1/FAILURE)
   Main PID: 6278 (code=exited, status=1/FAILURE)
     Status: "Terminating..."
      Error: 65 (Package not installed)

Feb 27 13:33:08 cosmos64 systemd-nspawn[6278]: /var/lib/machines/image.raw.zstd.raw: Couldn't identify a suitable partition table or file system.
Feb 27 13:33:08 cosmos64 systemd-nspawn[6278]: Note that the disk image needs to
Feb 27 13:33:08 cosmos64 systemd-nspawn[6278]:     a) either contain only a single MBR partition of type 0x83 that is marked bootable
Feb 27 13:33:08 cosmos64 systemd-nspawn[6278]:     b) or contain a single GPT partition of type 0FC63DAF-8483-4772-8E79-3D69D8477DE4
Feb 27 13:33:08 cosmos64 systemd-nspawn[6278]:     c) or follow https://systemd.io/DISCOVERABLE_PARTITIONS
Feb 27 13:33:08 cosmos64 systemd-nspawn[6278]:     d) or contain a file system without a partition table
Feb 27 13:33:08 cosmos64 systemd-nspawn[6278]: in order to be bootable with systemd-nspawn.
Feb 27 13:33:08 cosmos64 systemd[1]: [email protected]: Main process exited, code=exited, status=1/FAILURE
Feb 27 13:33:08 cosmos64 systemd[1]: [email protected]: Failed with result 'exit-code'.
Feb 27 13:33:08 cosmos64 systemd[1]: Failed to start Container image.raw.zstd.

journalctl -xeu [email protected]

Feb 27 13:33:08 cosmos64 systemd[1]: Starting Container image.raw.zstd...
-- Subject: A start job for unit [email protected] has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit [email protected] has begun execution.
-- 
-- The job identifier is 1521.
Feb 27 13:33:08 cosmos64 systemd-nspawn[6278]: /var/lib/machines/image.raw.zstd.raw: Couldn't identify a suitable partition table or file system.
Feb 27 13:33:08 cosmos64 systemd-nspawn[6278]: Note that the disk image needs to
Feb 27 13:33:08 cosmos64 systemd-nspawn[6278]:     a) either contain only a single MBR partition of type 0x83 that is marked bootable
Feb 27 13:33:08 cosmos64 systemd-nspawn[6278]:     b) or contain a single GPT partition of type 0FC63DAF-8483-4772-8E79-3D69D8477DE4
Feb 27 13:33:08 cosmos64 systemd-nspawn[6278]:     c) or follow https://systemd.io/DISCOVERABLE_PARTITIONS
Feb 27 13:33:08 cosmos64 systemd-nspawn[6278]:     d) or contain a file system without a partition table
Feb 27 13:33:08 cosmos64 systemd-nspawn[6278]: in order to be bootable with systemd-nspawn.
Feb 27 13:33:08 cosmos64 systemd[1]: [email protected]: Main process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- An ExecStart= process belonging to unit [email protected] has exited.
-- 
-- The process' exit code is 'exited' and its exit status is 1.
Feb 27 13:33:08 cosmos64 systemd[1]: [email protected]: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit [email protected] has entered the 'failed' state with result 'exit-code'.
Feb 27 13:33:08 cosmos64 systemd[1]: Failed to start Container image.raw.zstd.
-- Subject: A start job for unit [email protected] has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit [email protected] has finished with a failure.
-- 
-- The job identifier is 1521 and the job result is failed.

Used command to install the nspawn image:
sudo machinectl pull-raw --verify=checksum https://hub.nspawn.org/storage/archlinux/archlinux/raw/image.raw.zstd

Review the possibility to signing the images with the new Sigstore stack

@shibumi knows all the details about this, I just opened it for tracking.

Containers have no network

All containers don't have network.. This is something I would expect, so I will add it.

ubuntu/* and debian/* have no network

I just tested ubuntu/focal, ubuntu/jammy, and debian/sid.

The images were installed like this:

nspawn -i ubuntu/focal/tar

machinectl start ubuntu-focal-tar

machinectl login ubuntu-focal-tar

➜  ~ sudo machinectl login ubuntu-focal-tar
Connected to machine ubuntu-focal-tar. Press ^] three times within 1s to exit session.

Ubuntu 20.04 LTS focal pts/1

focal login: root
Password: 
Welcome to Ubuntu 20.04 LTS (GNU/Linux 6.2.1-arch1-1 x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management:     https://landscape.canonical.com
 * Support:        https://ubuntu.com/advantage

The programs included with the Ubuntu system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by
applicable law.

root@focal:~# ping www.google.de
ping: www.google.de: Temporary failure in name resolution

root@focal:~# apt update
Err:1 http://archive.ubuntu.com/ubuntu focal InRelease
  Temporary failure resolving 'archive.ubuntu.com'
Err:2 http://security.ubuntu.com/ubuntu focal-security InRelease
  Temporary failure resolving 'security.ubuntu.com'
Err:3 http://archive.ubuntu.com/ubuntu focal-updates InRelease
  Temporary failure resolving 'archive.ubuntu.com'
Reading package lists... Done        
Building dependency tree       
Reading state information... Done
55 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/focal/InRelease  Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/focal-security/InRelease  Temporary failure resolving 'security.ubuntu.com'
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/focal-updates/InRelease  Temporary failure resolving 'archive.ubuntu.com'
W: Some index files failed to download. They have been ignored, or old ones used instead.

fedora-34-tar on the other hand worked. Maybe you can help :)