You need to connect the Pi4 to a monitor and keyboard and run omv-firstaid to reconfigure the ethernet.
No other way.
Thank You. was hoping for a way without needing a monitor, but it worked and was painless.
Thank You
You need to connect the Pi4 to a monitor and keyboard and run omv-firstaid to reconfigure the ethernet.
No other way.
Thank You. was hoping for a way without needing a monitor, but it worked and was painless.
Thank You
Hi
I have a Pi4 32bit OS with OMV6 on SD with data on SSD.
Changing to OMV7 on 64bit
Used a spare Pi400 to setup OMV7, using new SD card and cloned SSD.
Got all my setup correct and functioning 100%
Now want to move the 64bit OS OMV7 SD card from the test Pi400, to my main Pi4
Pi4 is headless.
SD in to Pi4, and no IP address appears in the router ARP table.
Downloaded Angry IP and scanned full IP range and nothing listed.
Moved the SD card BACK to the Pi400, and shows up perfectly.
Advice please.
Any chance you are running the flashmemory plugin?
yes
ignore. 15 minutes later it's not sending mails again
ryecoaaron - I see this appears to be a common problem you working on.
Just an observation, in case it hints to the problem/ solution :
I had my email listed as the sender and the recipient. As soon as I changed the Notifications > Settings > Recipient to my gmail account, all the mails started flowing again.
Not sure if it's because the sender and recipient was the same, or if the sender and recipient are now completely different services ?
2c
- /path/to/custom/php.ini:/usr/local/etc/php/php.ini:ro
You are awesome as always !
I put the php.ini file in the same folder as the php-apache.yml file, and used the Absolute Path from the Shared Folders list to add the Volume to the Compose File.
Tested by making a small change to the php.ini file, Stopped and UP'd the Container, and changes reflected correctly.
new Compose File :
services:
php-apache:
image: php:8.2-apache
container_name: php-webserver
working_dir: /var/www/html
volumes:
- /srv/dev-disk-by-uuid-ab32bc62-5c9c-467c-8348-xxxxxxxx/www/www:/var/www/html
- /srv/dev-disk-by-uuid-ab32bc62-5c9c-467c-8348-xxxxxxxx/DocCompose/php-apache/php.ini:/usr/local/etc/php/php.ini:ro
ports:
- "80:80"
OMV7 on a Pi4.
Replacing an OMV6 setup.
Notification email settings identical between the 2 systems.
Test mail not coming thru. ( yes, checked spam folders ).
Notifications from Scheduled Tasks also not sending.
When System Reboot and system starts up, all emails suddenly come thru ( with their correct time stamp ).
In fact, I'm now getting DUPLICATE mails that came thru at the time of the last reboot.
Am I missing a setting ?
Select the php-apache example.
OMG !!!!! You make this so simple ! It works and the kettle hasn't even boiled yet !!
Thank You
html pages display, and the phpinfo.php displays.
I assume there's a config or settings page or file somewhere for php ?
Would that exist only in the docker Container and need to be recreated if the Container is recreated ?
edit ..
Been doing some googling, and it appears that php is installed in the new container with the default php.ini file.
To have a php.ini file that exists outside the Image / Container, a php.ini file could be placed in the Docker Compose folder ( same location as the php-apache.yml file, and have it added to the Image when the image is created in a DockerFile ?
Does this sound like a viable option ?
side note : It was previously mentioned to "use a sharedfolder that points to /srv/dev-disk-by-uuid-ab32bc62-5c9c-467c-8348-d53ccd5627e9/www for the data directory on the settings tab of the plugin"
I was unsure about this, as it would ( I think ) redirect all docker data usage for all docker containers to that 'www' shared folder. So after seeing the great php-apache option working, I removed the container, reset the data directory on the settings tab, and restarted Docket.
Everything still works, so it appears that the data directory ( listed in the settings tag ) does not have any effect on this Container.
side note : I have the OMV dashboard set to port 90, so port 80 is free for the web server.
I gave up on the nginx and php idea, and instead found a Compose file for Apache php :
services:
httpd:
image: httpd:2.4
volumes:
- /srv/dev-disk-by-uuid-ab32bc62-5c9c-467c-8348-d53ccd5627e9/www/www:/usr/local/apache2/htdocs/
ports:
- 80:80
restart: unless-stopped
It runs without generating any errors, and I can see the html pages from a browser. It's not running the php yet - it's simply listing the content of the php code in the browser, like a text editor view.
I think it's something to do with the apache config, but I can't find where to change that. The path that the apache page mentions, does not appear to exist on the Pi.
I am assuming it's hidden somewhere in the docker container.
tomorrow's another day. Thanks for trying to help. Very much appreciated.
You can install portainer on the compose plugin on omv 7
isn't that defeating the purpose of having the Compose service in OMV7 ?
Post the stack.
version: "2.1"
services:
nginx:
image: linuxserver/nginx
container_name: nginx
environment:
- PUID=1000
- PGID=1000
- TZ=Africa/Johannesburg
volumes:
- /srv/dev-disk-by-label-NAShd1/www:/config
ports:
- 80:80
- 443:443
restart: unless-stopped
Display More
in the Compose File, I changed the Volume to the ID ( I think the 'by label' was carried over from a previous upgrade from omv5 to omv6
Thanks Aaron
I'm more confused and understand less after wasting 10 hours on this problem today.
I simply can't grasp all this. Probably too old. I feel like I shouldn't have bought a car if I can't change an oil seal on a gearbox !
Going to revert back to the 32bit Pi OS with omv6 and probably stay with that until it breaks
Copy the stack into the compose plugin and start it. It is that simple. A portainer stack is a compose file.
that's the first thing I tried and it failed.
Wouldn't show the existing index.html page or the phpinfo.php page
It did? Using the compose plugin?
maybe I misunderstand how it worked. on OMV6 there was a Portainer Stack that created the Container, and I have php scripts in a shared folder on my SSD that I can run. So I am guessing that the php was installed in the container somehow.
php-apache example to the compose plugin
where would I find this ?
changing from OMV6 to OMV7 ( so removing Portainer ).
OMV6 had a docker container for nginx and php, but that does not function on OMV7.
So a suggestion I saw was to use an Apache Docker.
Using a Pi4
Are there any clear, simple, step-by-step instructions, or youtube vids, to do this from start to finish ?
Most of what I have found, is not for OMV7 or not for Pi architecture.
Alternatively, where would be the best place to look for someone to do this ( for a small fee, of course ) ?
My bad, didn't saw.
Then, check if the files are correct under the HOST PATH:
ls -al /srv/dev-disk-by-uuid-ab32bc62-5c9c-467c-8348-d53ccd5627e9/www
when I run that in a terminal, it lists all the correct files that exist in the path
Following advise from another post, upgrading to OMV7 :
here's my setup :
Pi4 machine #1 ( Pi41 ), 32 bit Lite OS, OMV6 ( upgraded previously from OMV5 )
Runs Docker and Portainer.
Using stacks, images & containers for : Portainer, Cloud Commander and nginx
have been told that 32 bt is on the way out, and best to upgrade to OMV7.
I also understand the OMV7 does not use Portainer. Instead uses the Compose Service.
Also Docker runs better on 64 bit.
So setting up another pi with a 64bit OS.
Pi4 machine #2 ( Pi42 ), 64 bit Lite OS, OMV7 ( installed and running )
Both Pi41 and Pi42 OMV have their System > Workbench > Port set to 90, so 192.168.1.xx:90 gets me to the OMV control panel on each Pi.
I am running both Pi41 and Pi42 on the home LAN at the same time ( each had unique IP address ).
Both Pi has a 250Gb SSD - both identical ( cloned ) , same ID. Both SSDs run on OMV6 Pi41 ( seperately ) and function 100% as expected.
On Pi42 on OMV7, I have set up Shared Folders, Users, permissions, etc as same as Pi41 OMV6, as much as I can work out.
Problem starts with Docker.
First was to set up Cloud Commander in a Container.
Went to Services > Compose > Files.
Add new, and copied code from Portainer Stack ( OMV6 Pi41 ) to a new OMV7 Compose File :
services:
web:
ports:
- 7000:8000
environment:
- TZ=Africa/Johannesburg
volumes:
- /srv/dev-disk-by-uuid-ab32bc62-5c9c-xxxx-xxxx-d53ccd56xxxx/DocCompose/CloudCommmander/~:/root
- /:/mnt/fs
image: valentinalexeev/rpi-cloudcmd
I had to change the 'volume' because the OMV6 ( upgraded from OMV5 ) still referenced the volume 'by Label'.
Used the 'Up' button to create the Container, and works perfectly.
I can browse to 192.18.1.xx:7000 and access Cloud Commander.
Problem is with making a Container for nginx to access a web site that I have on the ssd.
The OMV6 > portainer Stack contains :
services:
nginx:
image: linuxserver/nginx
container_name: nginx
environment:
- PUID=1000
- PGID=1000
- TZ=Africa/Johannesburg
volumes:
- /srv/dev-disk-by-label-NASxxxx/www:/config
ports:
- 80:80
- 443:443
restart: unless-stopped
Display More
I have changed the volume to the Mount Point for my shared www folder :
services:
nginx:
image: linuxserver/nginx
container_name: nginx
environment:
- PUID=1000
- PGID=1000
- TZ=Africa/Johannesburg
volumes:
- /srv/dev-disk-by-uuid-ab32bc62-5c9c-467c-8348-d53ccd5627e9/www:/config
ports:
- 80:80
- 443:443
restart: unless-stopped
Display More
URLs that work on OMV6 do not work on OMV7 :
for example :
but Cloud Commander works :
What am I missing ? I assume it's something to do with the copying of the code from the OMV6 Portainer Stack to the OMV7 Compose File ?