DEV Community

Cover image for How Have Fedora of Mine Been
Naufan Rusyda Faikar
Naufan Rusyda Faikar

Posted on • Updated on

How Have Fedora of Mine Been

I, sometimes, love being as a researcher. In just a minute or two, my machine, oftentimes, ended up be a mess. Hearing of Fedora thirty-four which has just officially launched, doing a fresh install of the operating system (OS) had been emerging in my mind, all the time. But how could clean installation clean up the mess? Nay, that is not possible! Once I got my hands dirty, everything will not be alright. Consequently, I have thoughts of keeping myself away from messing around for this time.

As many of people in many different communities have mentioned what is new in the thirty-four edition, followed by how-tos when installing Fedora for the first time, or even again, I have nothing more to share. Still and all, it is rather not a bad idea to capture and talk about decisions I have made.

Most of people will do update all the pre-installed packages on their newly installed operating system, so did I. On Fedora, to update/upgrade packages, we need to do:

$ sudo dnf --assumeyes upgrade

$ systemctl reboot
Enter fullscreen mode Exit fullscreen mode

Thereafter, I started to setup this armament of mine.


I have concerned that my cheap wireless earbuds is not working correctly on PipeWire. There are audio skips and out-of-sync issues, constantly. So, I have decided to switch back to PulseAudio by:

$ sudo dnf swap --allowerasing pipewire-pulseaudio pulseaudio
Enter fullscreen mode Exit fullscreen mode

I will give PipeWire a second chance after hearing that this issue is resolved in the upstream. Until then, we are done. Or until someone gives me more supported earbuds. LOL.


To play a wide variety of multimedia, especially those with restricted codecs, we need to:

# Enable the RPMFusion repositories
$ sudo dnf install$(rpm -E %fedora).noarch.rpm$(rpm -E %fedora).noarch.rpm

# Install the restricted codecs
$ sudo group upgrade --with-optional Multimedia
Enter fullscreen mode Exit fullscreen mode

So, I can now play all of them using the default video player on Fedora, GNOME Videos, or formerly known as Totem. I know, it is not the best choice, but it just worked for me.


Since my machine has a dedicated graphics processing unit (GPU), the GeForce GTX 10 Series for mobile, I have also grabbed the proprietary driver by:

$ sudo dnf install -y akmod-nvidia
Enter fullscreen mode Exit fullscreen mode

And then restart my machine once again.


We are all know that technology is changing too fast these days. They are unpredictable anymore. It seems like every day, new programming languages and frameworks are born. Sometimes they are solutions, sometimes they are new problems.

As a software developer, or even just a normal computer user, the need to testing out which tool works best cannot be avoided. This is the another reason why my Fedora-yey is getting bloated and unkempt by the day.

I was thinking to keep my host as minimum as possible by installing all the generic software—such as multimedia players, internet browsers, and text editors—on the host and separating all the specific things into container groups.

Gratefully, Fedora comes with Podman and Toolbox pre-installed. Let us take the curiosity out by looking into how I organised my workspaces into groups.

$ podman ps -a | grep -v toolbox
CONTAINER ID  IMAGE                                         COMMAND               CREATED       STATUS                      PORTS                   NAMES
45da333221a9                               5 weeks ago   Created           >80/tcp    dvwa
00cd783bf551                /               5 weeks ago   Exited (137) 5 weeks ago>80/tcp    bwapp
6d248675f778        npm start             5 weeks ago   Exited (0) 5 weeks ago>3000/tcp  juice-shop
feea59da1a18           /usr/bin/supervis...  5 weeks ago   Exited (0) 5 weeks ago>80/tcp    webgoat
7f791fa949e1             postgres              40 hours ago  Created                                             postgres
Enter fullscreen mode Exit fullscreen mode

For other cases, I need to have them installed on the root;

$ sudo podman ps -a
CONTAINER ID  IMAGE                                      COMMAND               CREATED      STATUS                    PORTS                                           NAMES
cef6fbe452f6  sh -c /bin/servic...  4 weeks ago  Exited (137) 4 weeks ago                                                  metasploitable
db82745c519b                                             2 weeks ago  Created         >3000/tcp,>3306/tcp  18235f9b87b5-infra
Enter fullscreen mode Exit fullscreen mode

Having those containers, I rarely boot up GNU/Linux OSes with GNOME Boxes. Although, I still need them for a couple of things.

You might noticed that all the above containers can be easily obtained by, for instance:

# Download the PostgreSQL image
$ podman pull

# Create and run a new PostgreSQL container
$ podman run --name postgres --network=host -e POSTGRES_PASSWORD=pass -d postgres

# Enter the PostgreSQL client
$ podman exec -it postgres psql -U postgres
Enter fullscreen mode Exit fullscreen mode

Each one is pre-configured by every great maintainers around the globe; nothing more to configure anything. But what if I want to customise a container from scratch? Meaning, just give me a rootfs (if I am not mistaken) and I will do the rest. In this case, Toolbox has some advantages over the others;

$ toolbox list

IMAGE ID      IMAGE NAME                                    CREATED
9c649cf455d4  7 weeks ago

25dba789f9c7  build-tool      13 days ago  exited
17e258afdc85  games           6 days ago   exited
b1263fcbb2f3  iot-dev         3 days ago   configured
788dea945c07  mobile-dev      7 days ago   configured
b68dcf5c322f  texlive         6 weeks ago  configured
709bab881755  web-dev         13 days ago  exited
6317f74b06ae  web-sec         5 weeks ago  exited
Enter fullscreen mode Exit fullscreen mode

Whensoever it is required to build a package from the source code, I will do so in the build-tool container and grab the executable to the host if needed. This is pretty much where I installed the -devel packages.

I have all games, with all the dependencies for the wine to run correctly, installed in the games container. Despite being not a pro gamer, but rather a programmer, I have included Steam as well.

Although we have installed the GPU driver and have fully access to the GPU from the box, out-of-the-box, until now we need to install the driver again inside the box (read: container). There is a discussion and work-in-progress solution for this.

By the way, do not forget to set the launch game options with __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia %command% to every Steam games to run it using the Nvidia GPU.

For programming, I have iot-dev, mobile-dev, and web-dev containers, even though they can all be put together (not to-get-her, sorry) into a single container.

For writing, as I prefer LaTeX to LibreOffice Writer and Google Docs, I have created texlive container. Why not the host? Is not it a generic-purpose software? Because of:

$ sudo dnf install texlive-scheme-full
Enter fullscreen mode Exit fullscreen mode

There are so many packages that need to be installed, whoops, that is it.


Firefox is by default comes with Fedora Workstation installation. I love Firefox, she is a nice friend, not a pet. But I love Firefox Developer Edition more. So, sorry, got to move on. Unluckly, there is not any Firefox Developer Edition in the official Fedora repository. Therefore, I had to download the tar file, extract, and install it manually.

By the way, Firefox has its own way to get an update, thus need not to do it by hand. It means no more downloading, extracting, and installing it manually.

Apparently, Visual Studio Code (VSCode) Insider has no idea about this behaviour. But it is relatively easier to install compared to Firefox Developer Edition.

Besides these two, I have also installed Krita, GIMP, and Inkscape for daily use. For Krita, I am not using it for creating artworks, but for writing/sketching notes (please, do not blame me). For setting up my programmable mouse, I have Piper. For recording my screen, I have chosen Kooha. For connecting my desktop to mobile devices, I have been using GSConnect. And it goes on ... As everyone has their own preferences.


You might be wondering, how do I compile *.tex files? The host does not have LaTeX compiler, but the texlive container does. With Visual Studio Code, it is easy to remote access to the container.

First of all, let us run and enter the container:

$ toolbox enter texlive
Enter fullscreen mode Exit fullscreen mode

Second, give write permission to the /root directory for our user. This is important for the VSCode to write server configuration files to the /root. In spite of not the best workaround, I tend to change the ownership instead;

$ sudo chown -R naru /root
Enter fullscreen mode Exit fullscreen mode

Third, attach the VSCode to the running container named texlive. We need the Remote - Containers extension installed on the VSCode.

Forth, open a folder contains our LaTeX files.

Fifth, happy writing! You probably would like to install LaTeX Workshop extension for VSCode.

We actually need not to enter the texlive container, just run it. So, we can safely exit from the container now. Next time, make sure to run the container:

$ toolbox run -c texlive true
Enter fullscreen mode Exit fullscreen mode

before VSCode, if not already run.

That is all. Appreciate any feedback from all of you. Feel free to share your setup with us. Have a nice day!


Top comments (0)