![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/0943eca5-c4c2-4d65-acc2-7e220598f99e.png)
No - but wiping it off is no issue. If you drool on yourself I’m not gonna touch it
No - but wiping it off is no issue. If you drool on yourself I’m not gonna touch it
Fluids that exit the body is like this. Only exception is blood from your own kin and tears. Anything else gets very dirty once out of body. Sweat, urine, vomit etc
Spit in a cup and drink it and watch how your peers react.
It’s probably as your “backup plan” is faulty but they don’t want to embarrass you.
Can you see the data you copied inside the container? I’m quite sure you either don’t have the volume mounted, or the config files refers to a different folder than the gitea one did. Did your gitea container store data in sqlite as you are copying raw files rather than migrating a database?
I’d go with lxc instead of containers if you don’t fully understand docker. Overhead isn’t much different and you get a “normal server” where you can drop in forgejo to replace gitea
NVMe device names follow this pattern: nvme <number> n <namespace> , where: <number> is an integer that is assigned by Linux during the boot process. The first NVMe device that is detected is assigned 0
Docker can be many things - and portainer is a nice replacement for those using docker for running services. It’s got a great web interface. For automation and most development docker and compose is my pick. Also a good fit for those that only use X to spawn terminals.
This is nis and nfs
Nothing to see here
Literal translation of the Norwegian word for raccoon is Wasing-Bear
Spider-man 2: the game