<https://github.com/ublue-os/bazzite/blob/main/system_files/desktop/shared/usr/share/ublue-os/motd/t

T

TheSteve0•3/11/24, 12:45 AM

I wonder why there is no F39 distrobox image

J

j0rgeOP•3/11/24, 12:46 AM

:latest appears to be 39

T

TheSteve0•3/11/24, 12:46 AM

There is for toolbox but but not the other one

T

TheSteve0•3/11/24, 12:46 AM

yeah there is

T

TheSteve0•3/11/24, 12:46 AM

wait what

T

TheSteve0•3/11/24, 12:47 AM

I was looking in Host distros

T

TheSteve0•3/11/24, 12:47 AM

nevermind - I was never here

Jj0rge <https://github.com/ublue-os/bazzite/blob/main/system_files/desktop/shared/usr/s...

K

Kyle Gospo•3/11/24, 12:48 AM

That's the one

J

j0rgeOP•3/11/24, 12:51 AM

@jonasrosland plus I need your brain to start thinking about cool gamer stuff we can do with the motd. Like theme the thing based on cool community things, like make it look nintendo with ansi art during the next anniversary, or like have retro themes and stuff.

K

Krepta•3/11/24, 12:51 AM

Is there a way to boot into windows without a keyboard?

K

Krepta•3/11/24, 12:52 AM

I know dual boot isn't officially supported but was curious if there's some sort of grub script

KKrepta Is there a way to boot into windows without a keyboard?

M

matt_schwartz•3/11/24, 12:52 AM

dual boot is supported, it’s just with another Linux partition that isn’t afaik. what device?

K

Krepta•3/11/24, 12:52 AM

I'm using a legion go

K

Krepta•3/11/24, 12:52 AM

I shrunk the original windows partition before installing bazzite

Jj0rge @jonasrosland plus I need your brain to start thinking about cool gamer stuff we...

J

jonasrosland•3/11/24, 12:53 AM

I love stuff like that, so count me in.

KKrepta I'm using a legion go

M

matt_schwartz•3/11/24, 12:53 AM

ah I’m not sure if there’s a way to make the controller work in grub then. On the Ally you have to manually enter the BIOS with volume + during boot or else the controller doesn’t activate until the kernel gets loaded

M

matt_schwartz•3/11/24, 12:53 AM

you can probably select from the BIOS though?

K

Krepta•3/11/24, 12:54 AM

Even if both operating systems are on one drive?

Jjonasrosland I love stuff like that, so count me in.

J

j0rgeOP•3/11/24, 12:54 AM

also lots of the container stuff can always use another set of eyes, it's not as ootb as it should be, but can't quite figure it out.

KKrepta Even if both operating systems are on one drive?

M

matt_schwartz•3/11/24, 12:54 AM

As long as the bios has both partitions visible (which it should) then yes

K

Krepta•3/11/24, 12:54 AM

Oh cool. Didn't know bios could boot a specific partition. I'll give it a shot.

KKrepta I shrunk the original windows partition before installing bazzite

K

Kyle Gospo•3/11/24, 12:55 AM

If the controller isn't working in grub you might try https://github.com/ryanrudolfoba/SteamDeck-Clover-dualboot

GitHub

GitHub - ryanrudolfoba/SteamDeck-Clover-dualboot: Script to install...

Script to install Clover - a graphical boot manager for the Steam Deck. - ryanrudolfoba/SteamDeck-Clover-dualboot

K

Kyle Gospo•3/11/24, 12:55 AM

But no guarantees I'm afraid

M

matt_schwartz•3/11/24, 12:56 AM

I wish more devices would adopt the Deck controller’s lizard mode but it’s pretty niche

T

TheSteve0•3/11/24, 12:56 AM

Yeah I knew I had seen something special about podman in podman

[spousty@test-minidev mini-dev]$ minikube logs --file=logs.txt

❌  Exiting due to GUEST_STATUS: Unable to get machine status: state: unknown state "minikube": sudo -n podman container inspect minikube --format=<no value>: exit status 1
stdout:

stderr:
sudo: podman: command not found


╭───────────────────────────────────────────────────────────────────────────────────────────╮
│                                                                                           │
│    😿  If the above advice does not help, please let us know:                             │
│    👉  https://github.com/kubernetes/minikube/issues/new/choose                           │
│                                                                                           │
│    Please run `minikube logs --file=logs.txt` and attach logs.txt to the GitHub issue.    │
│    Please also attach the following file to the GitHub issue:                             │
│    - /tmp/minikube_logs_b0abc3044fdf662878872600b82b718f3c77b46c_0.log                    │
│                                                                                           │
╰───────────────────────────────────────────────────────────────────────────────────────────╯

[spousty@test-minidev mini-dev]$ minikube logs --file=logs.txt

❌  Exiting due to GUEST_STATUS: Unable to get machine status: state: unknown state "minikube": sudo -n podman container inspect minikube --format=<no value>: exit status 1
stdout:

stderr:
sudo: podman: command not found


╭───────────────────────────────────────────────────────────────────────────────────────────╮
│                                                                                           │
│    😿  If the above advice does not help, please let us know:                             │
│    👉  https://github.com/kubernetes/minikube/issues/new/choose                           │
│                                                                                           │
│    Please run `minikube logs --file=logs.txt` and attach logs.txt to the GitHub issue.    │
│    Please also attach the following file to the GitHub issue:                             │
│    - /tmp/minikube_logs_b0abc3044fdf662878872600b82b718f3c77b46c_0.log                    │
│                                                                                           │
╰───────────────────────────────────────────────────────────────────────────────────────────╯

[spousty@test-minidev mini-dev]$ minikube logs --file=logs.txt

❌  Exiting due to GUEST_STATUS: Unable to get machine status: state: unknown state "minikube": sudo -n podman container inspect minikube --format=<no value>: exit status 1
stdout:

stderr:
sudo: podman: command not found


╭───────────────────────────────────────────────────────────────────────────────────────────╮
│                                                                                           │
│    😿  If the above advice does not help, please let us know:                             │
│    👉  https://github.com/kubernetes/minikube/issues/new/choose                           │
│                                                                                           │
│    Please run `minikube logs --file=logs.txt` and attach logs.txt to the GitHub issue.    │
│    Please also attach the following file to the GitHub issue:                             │
│    - /tmp/minikube_logs_b0abc3044fdf662878872600b82b718f3c77b46c_0.log                    │
│                                                                                           │
╰───────────────────────────────────────────────────────────────────────────────────────────╯

[spousty@test-minidev mini-dev]$ minikube logs --file=logs.txt

❌  Exiting due to GUEST_STATUS: Unable to get machine status: state: unknown state "minikube": sudo -n podman container inspect minikube --format=<no value>: exit status 1
stdout:

stderr:
sudo: podman: command not found


╭───────────────────────────────────────────────────────────────────────────────────────────╮
│                                                                                           │
│    😿  If the above advice does not help, please let us know:                             │
│    👉  https://github.com/kubernetes/minikube/issues/new/choose                           │
│                                                                                           │
│    Please run `minikube logs --file=logs.txt` and attach logs.txt to the GitHub issue.    │
│    Please also attach the following file to the GitHub issue:                             │
│    - /tmp/minikube_logs_b0abc3044fdf662878872600b82b718f3c77b46c_0.log                    │
│                                                                                           │
╰───────────────────────────────────────────────────────────────────────────────────────────╯

TTheSteve0 Yeah I knew I had seen something special about podman in podman ``` [spousty@tes...

K

Kyle Gospo•3/11/24, 12:57 AM

If distrobox, you can:

ln -s /usr/bin/distrobox-host-exec /usr/bin/podman

ln -s /usr/bin/distrobox-host-exec /usr/bin/podman

K

Kyle Gospo•3/11/24, 12:58 AM

Then it'll just run what's on the host

K

Kyle Gospo•3/11/24, 12:58 AM

And be able to make new containers

T

TheSteve0•3/11/24, 12:59 AM

Hmmm that's not the advice distrobox gives - but maybe their advice is so caches are not share
https://github.com/89luca89/distrobox/blob/main/docs/useful_tips.md#using-podman-inside-a-distrobox

GitHub

distrobox/docs/useful_tips.md at main · 89luca89/distrobox

Use any linux distribution inside your terminal. Enable both backward and forward compatibility with software and freedom to use whatever distribution you’re more comfortable with. Mirror available...

T

TheSteve0•3/11/24, 1:00 AM

I can't get minikube to start so if I have to that command in minikube it won't work. If I can do it in my Host OS then \0/

T

TheSteve0•3/11/24, 1:00 AM

same problem with Docker as well
https://github.com/89luca89/distrobox/blob/main/docs/useful_tips.md#using-docker-inside-a-distrobox

GitHub

distrobox/docs/useful_tips.md at main · 89luca89/distrobox

Use any linux distribution inside your terminal. Enable both backward and forward compatibility with software and freedom to use whatever distribution you’re more comfortable with. Mirror available...

Jjonasrosland Ohhh! Of course, happy to. I’m the ED over at https://hitsave.org, a 501(c)(3) n...

D

drumandbase-2•3/11/24, 1:12 AM

Neat. Any overlap with Internet Archive's work, notably Internet Arcade?

KKyle Gospo If distrobox, you can: `ln -s /usr/bin/distrobox-host-exec /usr/bin/podman`

T

TheSteve0•3/11/24, 1:13 AM

Tried it but no love

 Exiting due to MK_ADDON_ENABLE_PAUSED: enabled failed: get state: unknown state "minikube": sudo -n podman container inspect minikube --format=<no value>: exit status 1
stdout:

stderr:
/usr/bin/podman: line 189: XDG_RUNTIME_DIR: unbound variable


╭───────────────────────────────────────────────────────────────────────────────────────────╮
│                                                                                           │
│    😿  If the above advice does not help, please let us know:                             │
│    👉  https://github.com/kubernetes/minikube/issues/new/choose                           │
│                                                                                           │
│    Please run `minikube logs --file=logs.txt` and attach logs.txt to the GitHub issue.    │
│    Please also attach the following file to the GitHub issue:                             │
│    - /tmp/minikube_addons_d026ddbe70c5edc929b895aeb1e0c4ae9a4aae82_0.log                  │
│                                                                                           │
╰───────────────────────────────────────────────────────────────────────────────────────────╯

 Exiting due to MK_ADDON_ENABLE_PAUSED: enabled failed: get state: unknown state "minikube": sudo -n podman container inspect minikube --format=<no value>: exit status 1
stdout:

stderr:
/usr/bin/podman: line 189: XDG_RUNTIME_DIR: unbound variable


╭───────────────────────────────────────────────────────────────────────────────────────────╮
│                                                                                           │
│    😿  If the above advice does not help, please let us know:                             │
│    👉  https://github.com/kubernetes/minikube/issues/new/choose                           │
│                                                                                           │
│    Please run `minikube logs --file=logs.txt` and attach logs.txt to the GitHub issue.    │
│    Please also attach the following file to the GitHub issue:                             │
│    - /tmp/minikube_addons_d026ddbe70c5edc929b895aeb1e0c4ae9a4aae82_0.log                  │
│                                                                                           │
╰───────────────────────────────────────────────────────────────────────────────────────────╯

 Exiting due to MK_ADDON_ENABLE_PAUSED: enabled failed: get state: unknown state "minikube": sudo -n podman container inspect minikube --format=<no value>: exit status 1
stdout:

stderr:
/usr/bin/podman: line 189: XDG_RUNTIME_DIR: unbound variable


╭───────────────────────────────────────────────────────────────────────────────────────────╮
│                                                                                           │
│    😿  If the above advice does not help, please let us know:                             │
│    👉  https://github.com/kubernetes/minikube/issues/new/choose                           │
│                                                                                           │
│    Please run `minikube logs --file=logs.txt` and attach logs.txt to the GitHub issue.    │
│    Please also attach the following file to the GitHub issue:                             │
│    - /tmp/minikube_addons_d026ddbe70c5edc929b895aeb1e0c4ae9a4aae82_0.log                  │
│                                                                                           │
╰───────────────────────────────────────────────────────────────────────────────────────────╯

 Exiting due to MK_ADDON_ENABLE_PAUSED: enabled failed: get state: unknown state "minikube": sudo -n podman container inspect minikube --format=<no value>: exit status 1
stdout:

stderr:
/usr/bin/podman: line 189: XDG_RUNTIME_DIR: unbound variable


╭───────────────────────────────────────────────────────────────────────────────────────────╮
│                                                                                           │
│    😿  If the above advice does not help, please let us know:                             │
│    👉  https://github.com/kubernetes/minikube/issues/new/choose                           │
│                                                                                           │
│    Please run `minikube logs --file=logs.txt` and attach logs.txt to the GitHub issue.    │
│    Please also attach the following file to the GitHub issue:                             │
│    - /tmp/minikube_addons_d026ddbe70c5edc929b895aeb1e0c4ae9a4aae82_0.log                  │
│                                                                                           │
╰───────────────────────────────────────────────────────────────────────────────────────────╯

T

TheSteve0•3/11/24, 1:21 AM

Interesting this is minikube specific. If I run

podman run  --name some-postgres -e POSTGRES_PASSWORD=mysecretpassword -d postgres  docker.io/library/postgres

podman run  --name some-postgres -e POSTGRES_PASSWORD=mysecretpassword -d postgres  docker.io/library/postgres

it works fine

T

TheSteve0•3/11/24, 1:23 AM

I take it back. The command runs but it does not actually start a working container

podman logs some-postgres
/usr/local/bin/docker-entrypoint.sh: line 351: /docker.io/library/postgres: No such file or directory

podman logs some-postgres
/usr/local/bin/docker-entrypoint.sh: line 351: /docker.io/library/postgres: No such file or directory

podman logs some-postgres
/usr/local/bin/docker-entrypoint.sh: line 351: /docker.io/library/postgres: No such file or directory

podman logs some-postgres
/usr/local/bin/docker-entrypoint.sh: line 351: /docker.io/library/postgres: No such file or directory

T

TheSteve0•3/11/24, 1:24 AM

OK dinner time and a bunch of work with not much to show for it

KKyle Gospo If the controller isn't working in grub you might try https://github.com/ryanrud...

K

Krepta•3/11/24, 1:33 AM

Very cool!

T

TheSteve0•3/11/24, 1:45 AM

@j0rge what was the problem if I used Qemu in distrobox?

J

j0rgeOP•3/11/24, 1:45 AM

dunno

S

Simisear•3/11/24, 2:04 AM

does Bazzite have PulseAudio by default?

SSimisear does Bazzite have PulseAudio by default?

K

Kyle Gospo•3/11/24, 2:08 AM

Pipewire & Wireplumber

S

Simisear•3/11/24, 2:08 AM

ah, because im playing lethal company with friends and it says my input device was pulseaudio

SSimisear ah, because im playing lethal company with friends and it says my input device w...

K

Kyle Gospo•3/11/24, 2:08 AM

It's pipewire-pulse

K

Kyle Gospo•3/11/24, 2:09 AM

That's a wine default behavior

S

Simisear•3/11/24, 2:09 AM

ahhh

S

Simisear•3/11/24, 2:09 AM

like how its running on xwayland

K

Kyle Gospo•3/11/24, 2:09 AM

Yep

V

Valerie•3/11/24, 3:55 AM

Fun new "Maybe yuzu replacements" working in bazzite

V

Valerie•3/11/24, 3:55 AM

They have a flatpak but this is just a binary I built in an arch distrobox per their instructions.

VValerie Fun new "Maybe yuzu replacements" working in bazzite

K

Kyle Gospo•3/11/24, 4:09 AM

Nice! What was it?

<https://github.com/ublue-os/bazzite/blob/main/system_files/desktop/shared/usr/share/ublue-os/motd/t

Similar Threads

Similar Threads

Similar Threads