Shion Tanaka

I opened new issue. see https://github.com/containers/podman/issues/21548

This issue has been fixed by https://github.com/docker/roadmap/issues/262.

To activate Rosetta, you must mount the Rosetta directory on your Linux OS and add the magic code to binfmt_misc. Some users may want to remove this as an afterthought....

@baude I appreciate your review and your comments ! The latest commit(0ca90ce) was written before I read your comment, but I pushed it forward to move this PR. I will...

Thank you all for your comments and reviews. The implementation of common (containers.conf) and the removal of the `--rosetta` option(init/set) is working well in my environment. My understanding is that...

I wrote a simple process flow (each labels and vars are not an exact name, but to get a sense of the true/false flow). (mermaid graphs are not displayed on...

@rhatdan I did gofmt. And changed the SELinux context label of the Rosetta directory mount to `nfs_t`. When I first started working on this PR, `nfs_t` was problematic. Now the...

Here is my plan for Rosetta activation. Activating Rosetta requires two steps. 1. Mount the Rosetta directory 2. Register the Rosetta runtime binary as the handler You can use systemd-binfmt...

Enabled rosetta-activation.service and removed the process of executing services via ssh. The systemd error when `rosetta=false` has been fixed by ensuring that ExecStart* always ends with true. `/bin/sh -c "~...

> With a simple unit file, this works for me without a dependency issue: @cfergeau Thank you for your comment! I was indeed able to enable it with `Before=` as...