To get USB devices working inside a container, you need to map the device into the container, which can be tricky—especially if you’re running rootless containers.
If you’re on Linux and want to avoid complicated setups with user namespaces, groups, or messing with udev rules, the easiest way to start is by manually recreating the device node inside a folder you control (like where your config is stored) using mknod.
For example, if your USB device is /dev/ttyUSB0:
Run
ls -l /dev/ttyUSB0
You should see output like:
crw-rw---- 1 root dialout 188, 0 Jan 1 1970 /dev/ttyUSB0
Note the major (188) and minor (0) numbers.
Change directory to the folder where you want to create the "clone" device node, then run:
sudo mknod -m 666 ttyUSB0 c 188 0
(Use the major/minor numbers from your device — they differ by device.)
This will create a device readable and writeable by anyone on the system so perhaps consider changing the mode from 666 to 660 and/or chown the file afterwards to your user and group. As I said, this is HACKY and not a secure solution.
You will now have a device file you can then pass into your container with the Docker/PODMAN option:
--device /path/to/your/folder/ttyUSB0:/dev/ttyUSB0
I realize this is a pretty hacky and insecure workaround—feel free to downvote or ignore if you want something cleaner. But it’s a quick way to get your USB device accessible inside the container to get started. Later on, you can look into proper handling with udev or other methods if security is important.
If you use Windows, you are on your own unfortunately, I do not have experience with podman/docker in Windows environments.
Subtitles are not always simple text files in the source. They can come in various formats like SRT, WebVTT, Teletext, and VobSub—if they are present at all.
To integrate them into WebM, you must first determine if they exist, ensure they have the correct language tags (and tag them properly if they don’t), then extract them, convert them into a format compatible with the player, and finally remux them alongside the video and audio. This process can easily fail in an automated workflow if any of these conditions are unmet or if the subtitle format is incompatible.
Given this complexity, it’s understandable why many choose to avoid the effort rather than addressing whether WebM supports subtitles.
I am not defending anyone, but the process of it all makes it understandable, at least for me.
It's always been there in the add-on, why they removed it as a base feature beats me, but I feel they are going down the "Google route", remove all that works and replace it with what you never asked for.
Google used to hold a lot of nice services and features, including Chromecast. Why kill something that worked so well for so many people?
It could definitely be stress-related, especially if you had a particularly bad night of sleep before this started.
When you don’t sleep well, your body can reset its cortisol production cycle. Cortisol—the hormone tied to stress and alertness—typically starts rising in the early hours of the morning, around 3–4 a.m., as part of a normal circadian rhythm.
But if you're under even mild or subconscious stress, that spike can happen earlier or be stronger than usual, causing you to wake up prematurely and feel too alert to fall back asleep.
It's like your body's stuck in a "high alert" mode even if nothing obvious is triggering it.
Could be the birds that have already been mentioned as well, I am no expert, nor medical trained, but this reason is more common than you might think when waking up early. It's the same reason you might find yourself waking before the alarm when you really need to be on time, like before going on vacation and you cannot miss your flight.
(edit: added part of the sentence that got lost before posting)
I know this doesn’t directly solve your issue, and it might not help much now, but I wanted to share my experience just in case it’s useful.
When I had a similar problem after switching phones, what ended up helping was that I had 2FA enabled beforehand. In that case, after selecting the option to recover my account suddenly allowed me to receive a verification code via SMS—something that didn’t appear on the usual login screen, it was greyed out before selecting this option.
It probably won’t work if 2FA is disabled, but maybe it’s still worth checking if any recovery options that shows up helps. There might be a choice there that helps you resolve your problem as well.
In any case, good luck—I hope you’re able to get it sorted soon!
That tool was only included with Windows XP Professional, and even then, it was a command-line utility—so unless you were specifically looking for it or browsing through the %windir%\system32 directory, you probably wouldn’t have noticed it.
The article I referenced didn’t specify exactly which 32-bit versions it came with or when it was removed—it just mentioned that it was still included in 32-bit Windows after the DOS era. I didn’t write the article myself, so I can’t really speak to its accuracy.
Personally, I used that edline a lot back in the DOS days starting around 1985, until I switched to Notepad in Windows 95 and later to VIM when I moved to Linux after Windows 98. I never really checked for it in newer versions of Windows after that. A quick Google search confirmed it wasn’t included in XP Home, which would explain why you never saw it.
Edlin is a line editor, and the only text editor provided with early versions of IBM PC DOS,[1] MS-DOS and OS/2.[2] Although superseded in MS-DOS 5.0 and later by the full-screen MS-DOS Editor, and by Notepad in Microsoft Windows, it continues to be included in the 32-bit versions of current Microsoft operating systems.
edit: link and explanation of syntax used if anyone is interested. the w (write) and q (quit) commands made it somewhat similar to VI(M).
https://www.computerhope.com/edlin.htm
sorry, since you asked a question I just felt the need to clarify 🙂
The ISP products you mentioned really don’t seem consumer-friendly. I understand that ISPs might benefit from setting byte limits, since they incur costs for both inbound and outbound traffic to transit providers. However, from a consumer perspective, it's a poor deal—especially since most people don’t have the tools to manage their usage effectively and can burn through their quota far too quickly, just like you pointed out.
It all comes down to costs and earnings in the end for all products unfortunately.
I do not work there, just referenced the terms of conditions from their website, so you need to ask them the questions, but I think having a 1Gb connection with 30TB of seeding will eat up that pretty fast either way and also cause a mayhem of incoming connections, so it can hardly be considered private use (based on their definition)
Again, I have no reference to the company, so all questions should be forwarded to them not me. I simply gave a possible reasoning of the ban from their terms.
edit: added info about their definition of private use
that one was made in Russia according to the printed text..and in October 2022 if I read the date stamp correctly? and LEDVANCE is a company name, not product name, it was splitted out of OSRAMS LED division in 2016.
Ledvance GmbH, headquartered in Garching bei München, Germany, is a general lighting and smart home technology company. It was established in 2016 as a spin-off from Osram Licht AG. Since April 2018, Ledvance has been wholly owned by Chinese lighting company MLS.[3]
....
In April 2015, it was announced that Osram would divest its general lighting lamp business, which accounted for just over one-third of its workforce. In June 2015, the supervisory board of Osram Licht AG agreed to the divestment of their lamp division with products such as LED lamps, halogen lamps, and compact fluorescent lamps.[4][5] This divested division has been operating as a legally independent company under the name Ledvance since April 2016.
At the end of July 2016, Osram announced that Ledvance would be sold for more than €500 million[8] to a Chinese consortium consisting of investor IDG Capital, LED packaging manufacturer MLS, and Yiwu. The sale was completed on 3 March 2017, with economic effect as of 1 March 2017.[9][10][11] Due to the takeover, MLS gained distribution networks in Europe and the United States.[12][13] Since April 2018, MLS has been the sole owner of Ledvance
might be possible to use seabios as a UEFI boot and have it act as a bios (as it is a bios "emulator"), never been down that rabbit hole, but perhaps there is someone who has if you search / ask around
If you want a second attempt, this might help.
To get USB devices working inside a container, you need to map the device into the container, which can be tricky—especially if you’re running rootless containers.
If you’re on Linux and want to avoid complicated setups with user namespaces, groups, or messing with udev rules, the easiest way to start is by manually recreating the device node inside a folder you control (like where your config is stored) using mknod.
For example, if your USB device is /dev/ttyUSB0:
You will now have a device file you can then pass into your container with the Docker/PODMAN option: --device /path/to/your/folder/ttyUSB0:/dev/ttyUSB0
I realize this is a pretty hacky and insecure workaround—feel free to downvote or ignore if you want something cleaner. But it’s a quick way to get your USB device accessible inside the container to get started. Later on, you can look into proper handling with udev or other methods if security is important.
If you use Windows, you are on your own unfortunately, I do not have experience with podman/docker in Windows environments.