I have a domain name, do I need to do anything special at setup?

Zitat von Chipwingg

OK, I know it's getting kinda late.. so not sure how much further you want to go... but here's what I would do.

1. Download this ISO... https://cdimage.debian.org/deb…-11.3.0-amd64-netinst.iso

2. put that ISO on your installer w/ Etcher and boot it (Choose the graphical installation).. You'll need a mouse if you choose graphical, or if you're comfortable with the text installer, use it. The procedure is the same.

3. Go through the network connection, etc. and when it comes time to partition, choose "Manual". You should be able to see which drive you want to format as the OS.

Give it a swap partition.. probably 2-3 gigs should be plenty

The rest of the drive, make ext4, , format set to yes, and mount point should be /

Once that is done, make note of the drives location (/dev/sda, /sdb, whatever) continue with the install.

When it comes time, to install software... Uncheck everything but SSH server, and Standard System Utilities.

Finish install.

When it asks to install grub, choose manual, and manually choose the drive referenced earlier.. (ie, /dev/sda, /dev/sdb .. you shouldn't need any numbers after the drive letter).

Install grub and remove the installer, and reboot

Assuming you get the Debian prompt, we can go from there.

Zitat von Chipwingg

Thanks for those steps! Yeah, it’s too late to continue tonight. I have to wake up at 4.45 to go work tomorrow.

And will this method leave me with the exact same type of server as the normal installation? I.e., I won’t be able to tell the difference between the finished products?

Yes.. the only difference, is your user you create... will be in a shit ton of groups... where a user you create in the web panel, will only be in users by default. This is easy to modify once the OMV is installed on top of Debian

OK, so after you install Debian, log in with root, and get your IP

ip a

You said you have Ubuntu, so open an Ubuntu terminal and

ssh username@server.ip

The user name will be the one you created during the Debian install. Obviouslly serverip, is your server ip (debian doesn't allow root ssh by default).

Once logged in as your user, elevate to root

su -

and enter your root password.

Once your prompt changes to root

apt update

apt install wget sudo (they might already be installed, if they are fine, if not, install them)

Once that's done, paste this into the SSH session as root

wget -O - https://github.com/OpenMediaVault-Plugin-Developers/installScript/raw/master/install | sudo bash

Sit back and watch the show.

When it's done, go to your IP address in a web browser, and you should get the log in screen.

Default login is admin:openmediavault

Zitat von Chipwingg

Good to know. Before I resort to the dirty Debian method, I’m going to try flashing the iso onto a different brand and size of stick drive. If that doesn’t fix it (although I’m 90% sure it will) I will do Debian.

Now I just have to make sure I own a stick drive that’s different….

It's not really "dirty" (actually I prefer it).... but Volker writes the ISO's to basically remove most input from the user as it's presumed the user installing is.. probably inexperienced.... so it just kinda goes on autopilot. Well, sometimes as a result, you'll run into problems like you're having.

The Debian ISO, while slightly more complex, usually overcomes these issues, and then installing OMV on top of Debian is fairly trivial with the omv-extras script

Zitat von Chipwingg

I

Whew. After you taking the time to type that out, I might just do it anyways

LOL.

It honestly takes longer to type than actually do. The Debian install takes.. usually about 5-10min since you're not installing a ton of packages.

Installing OMV w/ the script, typically takes about 5-10min tops.

Zitat von Chipwingg

Hehe nice. I have installed Debian before so if I go that route it won’t be a huge challenge until I get to the omv part.

Is the thing that has happened (where I select a drive, and then cancelling it does nothing) considered a bug? Because if so, I’ll film it and send it so votdev can see it happening.

It's not really a bug, it just happens on occasion with USB to USB installs. USB to SATA, it almost never happens. Votdev does very little modification to the Debian installer. But I think because of the way the installer just sort of "auto partitions" the drive you choose, and doesn't really give you any other options... it causes an issue. And in your case, where your flash drives are both exactly the same.. you have no idea which one you installed to.

Zitat von Zoki

I do not want to make a long story about it, but ken0201 is effectivly root on the system! Does not matter if he is in the sudo group he can execute any command passwordless.

probably rm -rf /var as user ken0201 would not do any harm but just throws a few permission denied messages.

docker run --rm -v /:/rootfs debian  rm -rf /rootfs/var will just wipe the /var directory.

The reason is, that everyone in the group docker is allowed to access the docker socket. docker is running as root, so the container i spun up is running as root too.

This is the reason I have a seperate user docker-app just as a user to run processes inside the containers.

The same reason applies for not using the docker user (created automatically during install of docker) as a user inside your containers.

Alles anzeigen

I don't disagree w/ what you're saying.... with one caveat. I just done all this on a virtual machine (removing /var). Any damage appears to be isolated to the OS drive. So yes, OMV is wrecked and throws multiple errors during boot, the docker daemon is running but throwing errors when you try to do just about anything. But my data can't be messed with. I couldn't care less about the OS, I can have that back up in 40min. Trying to use that docker run command to remove a directory that is not on the root drive, just throws an error (as a user in the docker group). I even tried just removing the /srv directory.. and that didn't work at all. So unless I'm missing something what you're saying is true, but it really isn't relevant to my data.

Zitat von Zoki

Try mounting a /srv/dev.disk-by... directory and try (not on the real system).

Probably you could not remove files because you monted symlinks into the docker. As symlinks are not resolvable inside the container nothing bad happenes.

Have fun playing.

I am using this method on a server in a data center I do not have root / sudo privileges on to do the things which need to be done (Please don't tell anybody )

Alles anzeigen

I'm reinstalling my virtual machine now... I'll check in a sec (and actually for what it's worth.. I only had 1 container running, the wetty plugin provided by OMV... I had just set it up earlier to try zfs, as I'd never really messed with it). I'll be back in a minute.

So this is what I ended up with when I had no containers running. So it definitely can't remove a filesystem mountpoint, or a folder under said mount point.

oe@omv6-test:/$ id joe
uid=1000(joe) gid=100(users) groups=100(users),111(ssh),993(docker)
joe@omv6-test:/$ cd /srv
joe@omv6-test:/srv$ ls
dev-disk-by-uuid-f3bbe11d-9e2a-4620-acfc-9975c7f987c6  ftp     salt
dev-disk-by-uuid-f815b04f-b4cc-47d1-ad91-cda1270c759e  pillar
joe@omv6-test:/srv$ docker run hello-world

Hello from Docker!
This message shows that your installation appears to be working correctly.

To generate this message, Docker took the following steps:
 1. The Docker client contacted the Docker daemon.
 2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
    (amd64)
 3. The Docker daemon created a new container from that image which runs the
    executable that produces the output you are currently reading.
 4. The Docker daemon streamed that output to the Docker client, which sent it
    to your terminal.

To try something more ambitious, you can run an Ubuntu container with:
 $ docker run -it ubuntu bash

Share images, automate workflows, and more with a free Docker ID:
 https://hub.docker.com/

For more examples and ideas, visit:
 https://docs.docker.com/get-started/

joe@omv6-test:/srv$ docker run --rm -v /:/rootfs debian  rm -rf /srv/dev-disk-by-uuid-f815b04f-b4cc-47d1-ad91-cda1270c759e
Unable to find image 'debian:latest' locally
docker: Error response from daemon: Get "https://registry-1.docker.io/v2/": dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:57226->[::1]:53: read: connection refused.
See 'docker run --help'.
joe@omv6-test:/srv$ cd /srv/dev-disk-by-uuid-f815b04f-b4cc-47d1-ad91-cda1270c759e/
joe@omv6-test:/srv/dev-disk-by-uuid-f815b04f-b4cc-47d1-ad91-cda1270c759e$ ls
AppData  Test_Drive_1  aquota.group  docker
Home     Torrents      aquota.user   lost+found
joe@omv6-test:/srv/dev-disk-by-uuid-f815b04f-b4cc-47d1-ad91-cda1270c759e$ docker run --rm -v /:/rootfs debian  rm -rf /srv/dev-disk-by-uuid-f815b04f-b4cc-47d1-ad91-cda1270c759e/Test_Drive_1
Unable to find image 'debian:latest' locally
docker: Error response from daemon: Get "https://registry-1.docker.io/v2/": dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:49344->[::1]:53: read: connection refused.
See 'docker run --help'.
joe@omv6-test:/srv/dev-disk-by-uuid-f815b04f-b4cc-47d1-ad91-cda1270c759e$ 

So I installed a simple emby container (no symlinks... as you're right I use symlinks heavily in my compose files)...

version: "2.1"
services:
  emby:
    image: lscr.io/linuxserver/emby
    container_name: emby
    #network_mode: swag_default
    environment:
      - PUID=1000
      - PGID=100
    volumes:
      - /srv/dev-disk-by-uuid-f815b04f-b4cc-47d1-ad91-cda1270c759e/AppData/emby:/config
      - /srv/dev-disk-by-uuid-f815b04f-b4cc-47d1-ad91-cda1270c759e/Test_Drive_1/Media/Movies:/data/movies
    ports:
      - 8096:8096
    restart: unless-stopped

and then tried your command on the Movies folder....

joe@omv6-test:~$ docker run --rm -v /:/rootfs debian  rm -rf /srv/dev-disk-by-uuid-f815b04f-b4cc-47d1-ad91-cda1270c759e/Test_Drive_1/Media/Movies
Unable to find image 'debian:latest' locally
latest: Pulling from library/debian
67e8aa6c8bbc: Pull complete 
Digest: sha256:6137c67e2009e881526386c42ba99b3657e4f92f546814a33d35b14e60579777
Status: Downloaded newer image for debian:latest
joe@omv6-test:~$ docker run --rm -v /:/rootfs debian  rm -rf /srv/dev-disk-by-uuid-f815b04f-b4cc-47d1-ad91-cda1270c759e/Test_Drive_1/Media/
joe@omv6-test:~$ cd /srv/dev-disk-by-uuid-f815b04f-b4cc-47d1-ad91-cda1270c759e/Test_Drive_1/Media/
joe@omv6-test:/srv/dev-disk-by-uuid-f815b04f-b4cc-47d1-ad91-cda1270c759e/Test_Drive_1/Media$ ls
Movies
joe@omv6-test:/srv/dev-disk-by-uuid-f815b04f-b4cc-47d1-ad91-cda1270c759e/Test_Drive_1/Media$ 

At first glance, it appears to work... but then I cd'd, and the directory is clearly still there... I didn't have any data there (other than that Movies subfolder) which is clearly still there.

I'll come back to this on Monday or Tuesday when I'm off, as I have some brutal shifts this weekend and see if I come up with anything different.

Interesting points though.

Zitat von KM0201

I just installed the plugin, set up my shares and off I went.

Yep, the plugin should install zfs-dkms which will automatically compiling the module IF you have the headers installed. The plugins dependencies also include the headers but it can fail if you have multiple versions of the backport kernel installed (only one version of headers).