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

HOSTNAME is not set on f33 image #558

Open
A6GibKm opened this issue Sep 19, 2020 · 7 comments
Open

HOSTNAME is not set on f33 image #558

A6GibKm opened this issue Sep 19, 2020 · 7 comments
Labels

Comments

@A6GibKm
Copy link

@A6GibKm A6GibKm commented Sep 19, 2020

OS

Fedora Silverblue 33
toolbox 0.0.95

Issue

The enviromental variable HOSTNAME is not being set on toolbox, echo $HOSTNAME returns only a new line. This does not correspond to the behaviour in previous images.

Related issue: fedora-silverblue/issue-tracker#84

@A6GibKm A6GibKm added the 1. Bug label Sep 19, 2020
@HarryMichal
Copy link
Collaborator

@HarryMichal HarryMichal commented Sep 22, 2020

Hi @A6GibKm! I quickly tried to reproduce this but could not.

My steps were:

  • toolbox create (I run Fedora Silverblue 33 -> the f33/fedora-toolbox image was used)
  • toolbox enter
  • echo $HOSTNAME

The output of the last command was toolbox as currently expected. Is there something specific to your use-case I missed? What shell do you run?

@A6GibKm
Copy link
Author

@A6GibKm A6GibKm commented Sep 22, 2020

Not that I know of, I removed my .bashrc for testing purposes and enter a newly created toolbox and the issue persists. Also,

$ podman images
REPOSITORY                                     TAG     IMAGE ID      CREATED       SIZE
registry.fedoraproject.org/f33/fedora-toolbox  33      95dc9d4b0f27  2 weeks ago   327 MB
registry.fedoraproject.org/f32/fedora-toolbox  32      f7cf4b593fc1  6 months ago  360 MB
docker.io/library/fedora                       32      15fd256292f6  7 months ago  206 MB
@garrett
Copy link

@garrett garrett commented Sep 30, 2020

I don't see it here on my workstation, but I do see the missing $HOSTNAME in my test VM, even after a podman system reset.

$ podman images
REPOSITORY                                     TAG     IMAGE ID      CREATED      SIZE
registry.fedoraproject.org/f33/fedora-toolbox  33      95dc9d4b0f27  3 weeks ago  327 MB

The VM is completely vanilla (except for overlaying gitk for testing other toolbox/podman related issues), upgraded to the latest F33 beta Silverblue compose.

● ostree://fedora:fedora/33/x86_64/silverblue
                   Version: 33.20200929.n.0 (2020-09-29T08:06:48Z)
                BaseCommit: 215677333515cc11110cf016a4cbb021eb929b552f5ed25bb6d403c9f19c1a4a
              GPGSignature: Valid signature by 97A1AE57C3A2372CCA3A4ABA6C13026D12C944D0
           LayeredPackages: fedora-workstation-repositories gitk
@A6GibKm
Copy link
Author

@A6GibKm A6GibKm commented Oct 1, 2020

I also upgraded my second machine to f33, did a podman system reset and still the variable HOSTNAME is not set.

@dziq
Copy link

@dziq dziq commented Oct 28, 2020

I have exact the same issue. Rebased to f33, remove all toolboxes, create new one (f33) but echo $HOSTNAME outputs nothing.

@A6GibKm
Copy link
Author

@A6GibKm A6GibKm commented Oct 28, 2020

at least it is easy to patch via

# ~/.bashrc
if [ -f /README.md ]; then
    export HOSTNAME=toolbox
fi
@dziq
Copy link

@dziq dziq commented Oct 28, 2020

What is more hostid on f33 is 00000000 on f32 I have same numer as on host (a8c0a300). This issue is quite annoying while using mc (midnight commander).

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

Successfully merging a pull request may close this issue.

None yet
4 participants