I have verified the fix using systemd-container 249.11-0ubuntu3.10 from
jammy-proposed:
nr@clean-jammy-amd64:~$ apt-cache policy systemd-container
systemd-container:
Installed: 249.11-0ubuntu3.10
Candidate: 249.11-0ubuntu3.10
Version table:
*** 249.11-0ubuntu3.10 500
500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
500 http://security.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
100 /var/lib/dpkg/status
249.11-0ubuntu3.9 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
249.11-0ubuntu3.7 500
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
249.11-0ubuntu3 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
nr@clean-jammy-amd64:~$ machinectl image-status test
test
Type: directory
Path: /var/lib/machines/test
Hostname: ubuntu
OS: Ubuntu 22.04.3 LTS
RO: writable
Created: Mon 2023-08-28 15:44:25 EDT; 6min ago
nr@clean-jammy-amd64:~$ machinectl read-only test
nr@clean-jammy-amd64:~$ machinectl image-status test
test
Type: directory
Path: /var/lib/machines/test
Hostname: ubuntu
OS: Ubuntu 22.04.3 LTS
RO: read-only
Created: Mon 2023-08-28 15:44:25 EDT; 6min ago
nr@clean-jammy-amd64:~$ machinectl read-only test false
nr@clean-jammy-amd64:~$ machinectl image-status test
test
Type: directory
Path: /var/lib/machines/test
Hostname: ubuntu
OS: Ubuntu 22.04.3 LTS
RO: writable
Created: Mon 2023-08-28 15:44:25 EDT; 8min ago
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1991829
Title:
machinectl read-only does not work
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Focal:
Won't Fix
Status in systemd source package in Jammy:
Fix Committed
Status in systemd source package in Kinetic:
Fix Released
Bug description:
[impact]
machinectl read-only does not work
[test case]
On a system where the systemd machines dir is *not* on a btrfs volume
(e.g. it's on a normal ext4 fs), create an image 'test' and then:
$ sudo machinectl image-status test
test
Type: directory
Path: /var/lib/machines/test
Hostname: ubuntu
OS: Ubuntu 20.04.5 LTS
RO: writable
Created: Wed 2022-10-05 13:41:15 EDT; 34s ago
$ sudo machinectl read-only test
Could not mark image read-only: Access denied
[regression potential]
failure marking images ro or rw
[scope]
this is needed in all releases that include machinectl
this is fixed upstream by 137d162c42ed858613afc3d7493d08d4ae6d5c1b
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1991829/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
