Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tmp-is-dir broken symlink for /tmp by default #4884

Open
jmpolom opened this issue Mar 24, 2024 · 1 comment
Open

tmp-is-dir broken symlink for /tmp by default #4884

jmpolom opened this issue Mar 24, 2024 · 1 comment

Comments

@jmpolom
Copy link

jmpolom commented Mar 24, 2024

Describe the bug

tmp-is-dir: false appears to symlink /tmp to a non-existent directory by default, specifically /sysroot/tmp. This behavior is undocumented.

Reproduction steps

  1. Create a treefile to build an ostree/container from, and either set tmp-is-dir: false or leave it unset (default is false)
  2. Build the treefile into a container image
  3. Inspect the resulting container with (ex) podman run --rm registry.io/user/mycontainer file /tmp and you will observe the following output:
    /tmp: broken symbolic link to sysroot/tmp
    
  4. Can be confirmed with ls -lh / in the container, and absence of sysroot/tmp with ls -lh /sysroot

Expected behavior

At a minimum, this setting should not result in a broken symlink. The default probably should be true?

Actual behavior

A broken symlink for /tmp which is going to cause all manner of problem if you even manage to install the resulting tree/container or rebase to it.

System details

FCOS Stable, rpm-ostree 2024.2-2.fc39.x86_64

Additional information

No response

@jmpolom jmpolom changed the title tmp-is-dir symlinks /tmp to non-existent directory by default tmp-is-dir broken symlink for /tmp by default Mar 24, 2024
@cgwalters
Copy link
Member

The default probably should be true?

Yes, the defaults are stupid; we could almost certainly just change this one and not break anything, but I've been trying to be very conservative around breaking changes.

There's other defaults to change, like boot-location: modules. That could all probably be wrapped up into a global edition: 2024 flag.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants