Docker is not virtualisation, although it’s a common misconception.

A better way to think of it is a security wrapper around untrusted processes.

You can prove this for yourself by looking at all the processes running in a Docker host while one or more containers are running, you’ll see all the processes listed.

In other words, you don’t need a CPU capable of virtualisation to run Docker.

Use a bash command line:

https://stackoverflow.com/questions/6250698/how-to-decode-url-encoded-string-in-shell

This is what that looks like in real life:

https://github.com/aws/aws-cdk/issues/34892

When I last played with this a decade or so ago, there were several map tiling solutions in the geosciences that are self hosted.

From memory, “World Wind” is a good search term, but there’s others.

I use sshfs.

What is an Ubuntu LTS release?

An Ubuntu LTS is a commitment from Canonical to support and maintain a version of Ubuntu for ten years, with the initial five years available for free following Ubuntu’s mission. In April, every two years, we release a new LTS where all of the developments from the previous two years accumulate into one up-to-date, feature-rich release. These releases focus on performance enhancement and stability. The LTS is what we recommend to large scale enterprises, general users and businesses. However, for more dynamic users, every six months throughout those two years there are also developer releases. These releases are kept up-to-date and relevant, with the latest and greatest contributions, but are only supported for nine months at a time.

Source: https://ubuntu.com/blog/what-is-an-ubuntu-lts-release

The reason you pick an LTS release is so you get Long Term Support.

Use the support.

By moving to a non-LTS, you not only reduce the duration you get support, you also increase the frequency of doing updates. This is not desirable while you’re learning.

Pretty much the same.

Word of warning. Your /home directory contains your documents, but it also contains configuration files. If the packages you’re installing have different versions, you might discover that the config file for a different version doesn’t work on the version that’s installed. This isn’t universally the case, some applications are smart about this, others less so. You can find many of them as “hidden” “dot” files.

You can find all of them like this: find /home -type f -name '.*'

Explanation:

• find - the find command
• /home - the place to start looking
• -type f - find files only
• -name '.*' - find things only starting with a ‘.’

I hear your frustration and understand what you’re concerned about.

Ask yourself this.

Is the thing that I’ve discovered is broken today something that I’ve fixed before?

If you use the package manager that comes with your distribution and don’t install random software from the Internet, and don’t follow unverified procedures written by anyone with a keyboard, then the answer is almost certainly “no”.

I say this with the benefit of knowing what’s good practice and what isn’t. I can tell you that if you come at this with a “Microsoft Windows” approach, you’re likely to spend weeks, if not months in purgatory. It’s no different from migrating between MacOS and Windows, or vice-versa. You need to remember that just because Linux looks similar, it’s a different beast and is so by design.

I’d strongly recommend that you start using the machine with ONLY the packages available through the Ubuntu package manager. If you run into strife, you can ask for support. If you go outside that and you break something, you get to keep both parts – and truth be told – that’s true with any other operating system, just that the lines are not as blurred.

In Linux world many of the distributions can cross pollenate applications and solutions, but that requires experience that new users don’t (yet) have.

One way to deal with the “jump” is to keep your “old” Windows (or MacOS) machine around while you get comfortable with the lay of the land.

The thing that most people switching to Linux have forgotten is that this requires experience. You cannot expect to just jump into a new Operating System and take all your old habits with you. Think for example about the differences between iOS and Android, a world of difference.

So, keep at it. This frustration will pass.

Make sure you backup your /home directory regularly. That way if you ever blow something up and are left on your own, you can blow away the drive and start again, restore from your /home backup.

Meanwhile, keep asking questions.

Good luck.

Think of your workstation running Ubuntu Studio as new shoes that need running in.

I’ve been using Debian Linux as my primary desktop for over 25 years. The amount of downtime I experience is negligible. When I look at the sheer volume of MacOS updates requiring a reboot, or the absurd number of “fixes” pushed by Microsoft, I’m very content.

I read through the linked issue and then started on the one that was linked when the first issue was closed, even though the debate went on for several more years after it was closed and frankly gave up.

There was an unstructured debate between several people discussing what each of them thought was important and sometimes they even responded to each other.

One comment pointed out that this debate had gone on for seven years.

From my understanding, it’s been implemented in Chrome for all of those years.

The sky hasn’t fallen down, hell hasn’t frozen over and pigs still are rooted firmly on the ground.

If you ever wonder why people don’t use Firefox more, I cannot think of a better example.

As for a formal Mozilla position on the matter, I have yet to see anything beyond apathy.

The ability to have your browser communicate with a USB device.

https://en.m.wikipedia.org/wiki/WebUSB

Does it support WebUSB yet?

Does it support WebUSB yet?

Which tutorial were you following?

Which version of Ubuntu are you using?

The real question is: Why?

Here’s some answers to your question:

1. Backup your data, nuke the drive, start again.
2. chroot is the tool for the job. Backup your data before you accidentally nuke your drive.
3. Shrink the partition and write a new one in the empty space, but backup your data before you accidentally nuke your drive.
4. Connect an external drive, install on it, but backup your data before you accidentally nuke your drive.

Finally, the reason that the wiki didn’t help is that the question is asked by either a person with not enough experience, or one who doesn’t need the wiki. This is a non trivial process and you should backup your data before you proceed, lest you accidentally nuke your drive.

Edit:

Also, anything you break can be fixed … but only if you have a backup.

A till.

And an accounting package.

No hosting required.

With?

I run projects inside Docker on a VM away from important data. It allows me to test and restrict access to specific things of my choosing.

It works well for me.

Hands up if you have done this at least once in your life…