* Wed Oct 21 2026 marcus.schaefer@gmail.com
- Bump version: 3.2.9 → 3.2.10
* Wed Oct 21 2026 marcus.schaefer@gmail.com
- Make sure bubblewrap holds no host mounts
The current version of the bubblewrap-pilot manages the
root of the bwrap in overlay mounts below /var/tmp/bwrap_UID
This leaks the contents of the host root directory to a
location which allows others to read usually root private
data which is a security issue. The proposed fix operates
in two conditions:
1. if the rootfs and layers have no mount points below them,
the pilot sets everything up itself in its own namespace.
2. Mount points below, e.g. /: the pilot hands over to a new
helper command, sandbox-run, via sudo. The helper builds
the mounts as root in a private mount namespace, then drops
to your user for good, sets no_new_privs, and starts bwrap
there. Nothing is mounted on the host on either path.
* Wed Oct 21 2026 marcus.schaefer@gmail.com
- Bump version: 3.2.8 → 3.2.9
* Wed Oct 21 2026 marcus.schaefer@gmail.com
- Differentiate stderr and stdout channels
firecracker-pilot now keeps the command's stdout and stderr on
separate channels whenever its own stdout and stderr aren't both
terminals, for example app > out.txt or app 2>err.log. sci tries
to connect to that ports before it starts the command.
This Fixes #177
* Wed Oct 21 2026 marcus.schaefer@gmail.com
- Fix EOF wait in firecracker-pilot
The pilot reads just the exit status line and no longer waits
for the end of the stream.
* Wed Oct 21 2026 marcus.schaefer@gmail.com
- Fix handling of resume and force_vsock options
The runtime options resume and force_vsock were used at
registration time to create the VM cmdline boot_args
sci_resume and sci_force_vsock. Changing the runtime
options only without the boot_args caused weird side
effects in the behavior of the pilot. This commit
makes sure only the runtime options are taken into
account and the firecracker-pilot constructs the needed
boot_args from the runtime section.
* Wed Oct 21 2026 marcus.schaefer@gmail.com
- Fix race condition
The race came from stream_io on the host ending the whole session
when stdin hit EOF, even though the command in the VM was still running.
Now an early end of input just tells the command its input is over.
The pilot keeps relaying output until the guest closes the stream,
and the exit code arrives right after that. The 1s timeout now only
matters if the connection breaks.
* Wed Oct 21 2026 marcus.schaefer@gmail.com
- Fix firecracker exit code handling
So far the exit code of the calling program inside the VM was
lost in vsock mode. This commit makes sure the exit code is transfered
via a new vsock port to the caller. This Fixes #176
* Mon Oct 19 2026 marcus.schaefer@gmail.com
- Fix bwrap lookup in bubblewrwap-pilot
bubblewrap-pilot checks that bwrap exists by searching PATH,
but it then runs bwrap from the fixed path /usr/bin/bwrap.
As such the search doesn't make any sense. This commit
Fixes #174
* Mon Oct 19 2026 marcus.schaefer@gmail.com
- Use the which crate
Use the which crate to lookup a binary in PATH
Version: 3.1.45-160100.1.3
* Tue Aug 25 2026 marcus.schaefer@gmail.com
- Bump version: 3.1.44 → 3.1.45
* Sun Aug 23 2026 marcus.schaefer@gmail.com
- Drop extra rootfs image checksum test
The image is verified against the checksum record
fetched from its origin. This Fixes #103
* Sun Aug 23 2026 marcus.schaefer@gmail.com
- Update appstore
Also add checksum files for kis images
* Sun Aug 23 2026 marcus.schaefer@gmail.com
- Refactor firecracker checksum validation
So far the --kis-image pull method downloaded a tar file
and only verified the checksum of the root filesystem
image inside the tarball. However the tarball also contains
initrd and kernel files and the kiwi kis build also provides
an overall checksum file for the entire archive. This
commit refactors the code such that the entire tar file
is matched against its checksum. The appstore has been
already updated to provide these checksum files along
with the actual kis tar files. This Fixes #103
* Thu Aug 20 2026 marcus.schaefer@gmail.com
- Bump version: 3.1.43 → 3.1.44
* Thu Aug 20 2026 marcus.schaefer@gmail.com
- Update rsync options
Do not set extended attributes and acls as they failed to
transfer into the storage backend used by podman
* Thu Aug 20 2026 marcus.schaefer@gmail.com
- Bump version: 3.1.42 → 3.1.43
* Thu Aug 20 2026 marcus.schaefer@gmail.com
- Add --force option to remove command
Add --force option to flake-ctl firecracker remove
and fix the tab completion
* Wed Aug 19 2026 marcus.schaefer@gmail.com
- Bump version: 3.1.41 → 3.1.42
* Wed Aug 19 2026 marcus.schaefer@gmail.com
- Fixed firecracker pilot garbage collector
Only remove firecracker pilot related metadata files ending with .vmid
Version: 3.1.51-160000.1.1
* Wed Sep 02 2026 marcus.schaefer@gmail.com
- Bump version: 3.1.50 → 3.1.51
* Wed Sep 02 2026 marcus.schaefer@gmail.com
- Fix UDS socket setup
Check if there is an old UDS socket file still present prior
creating a new firecracker process. It must be deleted to allow
the new firecracker process to create and connect to it
* Wed Sep 02 2026 marcus.schaefer@gmail.com
- Fix firecracker network setup
Make sure a host route is added when assigning an IP address
to a firecracker instance (tap device)
* Wed Sep 02 2026 marcus.schaefer@gmail.com
- Update appstore
Make sure nfs-client exists in the firecracker images
* Wed Sep 02 2026 marcus.schaefer@gmail.com
- Bump version: 3.1.49 → 3.1.50
* Wed Sep 02 2026 marcus.schaefer@gmail.com
- Fix evaluation of %ignore_missing_volume_path
The argument parser splits option name and argument name
into single words which requires a different matching
logic in the loop iterating through the argument values
* Tue Sep 01 2026 marcus.schaefer@gmail.com
- Add new pilot_options section to the flake config
Allow to specify pilot options (that are options beginning with a %)
like %ignore_missing_volume_path in the flake yaml registration file.
A new registration argument named --pilot-option can be used to
permanently add a pilot option as part of the registration such
that it does not have to be passed at the commandline.
This is related to bsc#1274855
Assisted-by: Claude:claude-opus-4-6
* Tue Sep 01 2026 marcus.schaefer@gmail.com
- Bump version: 3.1.48 → 3.1.49
* Tue Sep 01 2026 marcus.schaefer@gmail.com
- Fixed Makefile
ghpages target missing the setup
* Tue Sep 01 2026 marcus.schaefer@gmail.com
- Bump version: 3.1.47 → 3.1.48
Version: 3.1.34-160000.1.1
* Mon Jul 06 2026 marcus.schaefer@gmail.com
- Bump version: 3.1.33 → 3.1.34
* Fri Jul 03 2026 marcus.schaefer@gmail.com
- Reverse showing progress logic
So far the user had to pass %silent to the call to make
the pilot stop showing progress information. The default
behavior to show progress information caused a lot of
confusion and breakage to script code calling an application
as a flake. It is rather unexpected that such progress
information is provided by default. This commit reverse the
logic such that a user has to provide %progress to see
the progress spinner while the pilot is working.
This Fixes #80
* Tue May 19 2026 marcus.schaefer@gmail.com
- Update documentation
* Mon May 18 2026 marcus.schaefer@gmail.com
- Update documentation
* Sat May 16 2026 marcus.schaefer@gmail.com
- Fix typo in documentation
* Sat May 16 2026 marcus.schaefer@gmail.com
- Update documentation
* Fri May 15 2026 marcus.schaefer@gmail.com
- Add ECR container sources to appstore
* Wed May 13 2026 marcus.schaefer@gmail.com
- Bump version: 3.1.32 → 3.1.33
* Wed May 13 2026 marcus.schaefer@gmail.com
- Call tools from /usr/sbin with abspath
Calling tools from /usr/sbin like mkfs.ext2 might not
be found by the calling shell if the PATH does not contain
/usr/sbin. Make sure to call these tools with an absolute
path. Also make sure to cleanup a broken filesystem artifact
when mkfs could not be called
* Wed May 13 2026 marcus.schaefer@gmail.com
- Update documentation
Update examples and architecture diagram
Version: 3.1.27-160000.1.1
* Mon Jan 26 2026 marcus.schaefer@gmail.com
- Bump version: 3.1.26 → 3.1.27
* Mon Jan 26 2026 marcus.schaefer@gmail.com
- Add support for --force option for remove
Add support for podman remove --force mode. In this
mode the referenced application will be force removed
and no sanity checks if this is pointing to a flake
registration will be done. Eventually missing files
do not cause an error.
* Mon Jan 26 2026 marcus.schaefer@gmail.com
- Fix spec file
Allow to build for Fedora, fix packager e-mail
* Mon Jan 26 2026 marcus.schaefer@gmail.com
- Bump version: 3.1.25 → 3.1.26
* Mon Jan 26 2026 marcus.schaefer@gmail.com
- Allow force registration with arbitrary data
When using --force also register even if the eventually
conflicting file does not belong to a flake registration
* Sat Jan 24 2026 marcus.schaefer@gmail.com
- Add --force option for register command
Allow to force writing the registration even if a
registration of the same name already exists. Also
update the man pages.
* Sat Jan 24 2026 marcus.schaefer@gmail.com
- Bump version: 3.1.24 → 3.1.25
* Sat Jan 24 2026 marcus.schaefer@gmail.com
- Improve command debug log
Make sure the command called is part of the log message
and not only the arguments
* Sat Jan 24 2026 marcus.schaefer@gmail.com
- drop obsolete permission settings
With the proper user vs. system wide setup there is no
need for the hacky permission adaptions. This also
improves the runtime performance
* Sat Jan 24 2026 marcus.schaefer@gmail.com
- Fixup flake lookup
system wide first, then user specific
Version: 3.1.22-160000.1.1
* Thu Sep 04 2025 marcus.schaefer@gmail.com
- Bump version: 3.1.21 → 3.1.22
* Thu Sep 04 2025 marcus.schaefer@gmail.com
- Fixes to use flakes as normal user
Running a flake is a container based instance provisioning
and startup. Some part of this process requires root permissions
for example mounting the container instance store for the
provisioning step. This commit fixes the required calls to
be properly managed by sudo.
* Thu Aug 21 2025 marcus.schaefer@gmail.com
- Bump version: 3.1.20 → 3.1.21
* Thu Aug 21 2025 marcus.schaefer@gmail.com
- seed from entropy
* Thu Aug 21 2025 marcus.schaefer@gmail.com
- Fix assignment of random sequence number
We should use a seed for the sequence as described in
https://rust-random.github.io/book/guide-seeding.html#a-simple-number
In addition the logic when a random sequence number should
be used was wrong and needed a fix regarding resume and
attach type flakes which must not use a random sequence
* Tue Aug 19 2025 marcus.schaefer@gmail.com
- Pass --init option for resume type flakes
In resume mode a sleep command is used to keep the container
open. However, without the --init option there is no signal
handling available. This commit fixes it
* Tue Aug 19 2025 marcus.schaefer@gmail.com
- Revert "kill prior remove when using %remove flag"
This reverts commit 06c7d4aa71f74865dfecba399fd08cc2fde2e1f2.
no hard killing needed with the event loop entrypoint
* Tue Aug 19 2025 marcus.schaefer@gmail.com
- Fixed CVE-2025-55159 slab: incorrect bounds check
Update to slab 0.4.11 to fix the mentioned CVE.
This Fixes bsc#1248004
* Tue Aug 19 2025 marcus.schaefer@gmail.com
- Apply clippy fixes
* Tue Aug 19 2025 marcus.schaefer@gmail.com
- Create sequence number for the same invocation
If a flake which is not a resume or attach flake is called twice
with the same invocation arguments an error message is displayed
to give this invocation a new name via the @NAME runtime option.
This commit makes this more comfortable and automatically assigns
a random sequence number for the call if no @NAME is given.
Version: 3.1.19-160000.2.2
* Wed Jun 25 2025 marcus.schaefer@gmail.com
- Bump version: 3.1.18 → 3.1.19
* Wed Jun 25 2025 marcus.schaefer@gmail.com
- Fix CVE-2025-3416
rebuild of the tool also inherits openssl in a version that
fixes the above mentioned CVE. This fixes bsc#1242680
* Wed Jun 25 2025 marcus.schaefer@gmail.com
- Fix CVE-2025-5791
Switch to uzers crate as actively maintained fork of the
unmaintained users crate. This Fixes bsc#1244207
* Wed Feb 26 2025 marcus.schaefer@gmail.com
- Fix firecracker requirement
Require firefracker only for TW as it exists in no
other version of SUSE. In case the firecracker-pilot
is installed on a system that has no firecracker it
must be installed to this system in an alternative
way which is easily possible because firefracker
is also a rust application only depending on libc
* Tue Feb 11 2025 marcus.schaefer@gmail.com
- Bump version: 3.1.17 → 3.1.18
* Tue Feb 11 2025 marcus.schaefer@gmail.com
- Style fixes
* Tue Feb 11 2025 marcus.schaefer@gmail.com
- Fix error handling for container check methods
The condition to setup permissions and redo the call
was done when the exec of the call was not possible.
But this is not the right place to check for a permission
denied error. This commit fixes the evaluation of the
error data
* Tue Feb 11 2025 marcus.schaefer@gmail.com
- Bump version: 3.1.16 → 3.1.17
* Tue Feb 11 2025 marcus.schaefer@gmail.com
- Don't use perform for bool status methods
The perform() call checks the status code and raises an
ExecutionError. This does not allow us to return a
false boolean. Use output() call instead
* Tue Feb 11 2025 marcus.schaefer@gmail.com
- Bump version: 3.1.15 → 3.1.16