thanks alot ryecoaaron , it work fine now i got portainer back ... now, i have to read more to use integrated use of docker i guess ...
Sry for didn't read the 1st page
Beiträge von bart70
-
-
Oh ... sorry, i didn't think about read the 1st post ... may i go to bed and look that tomorrow , that's safer for my datas ..
thanks for the link, i'll study it , and i'll write here if it's ok
-
on one NAS, yes portainer is still there but not on the one i've done the part 1
I read the guide, but true , i didn't read the 44 pages of this topic ... i'm bad in english, so it's a bit hard for me , take ages ... should i read this 44 pages ? -
Hi
I've updated my OMV and now, there is the new plugin.
I've done the part 1 of the guide here : Guide: Using the new docker plugin
but i'm stuck on part 2. I don't find the "stack" button ... and i think i didn't use stacks, just containers ... I'm a bit noob with docker, but it was easy for my to make my few needs to work...
I see my containers in services>compose>stats , nothing about others containers, i see only the started one .
Thanks a lot for your help, i have 2 nas updated and i can't use my containers anymore -
same for me.Update OMV6 broke my portainer, [tt]apt install apparmor apparmor-utils auditd and reinstalling portainer fixed it for me.[/
-
thanks you very much, it's working fine !
-
Hi,
I got 2 NAS , with almost the same setup. They are on OMV6.
They got 1 SSD where i installed omv and some SATA HDD in merge FS. As far i can't put my plex data base ()sqlite3 problem) on my mergeFS, i'd like to use the SSD.
On both systems, the SSD aren't visible.
My screenshots are from the same NAS, The SSD i'd like to use is the sdc :
i've tryed to mount it but omv doesn't see it
i've tryed to create a file system, it's the same.
Thanks for the help
-
i did this , all un web gui:
uninstall docker
apt-clean
reboot
install docker
install portainer
It's work !! thanks for idea !!
-
well, i need portainer to use docker (i'm really bad with CLI)
when i try to reinstall it, it failed (i removed and reinstalled) :
Code
Alles anzeigenDocker storage :: /var/lib/docker Agent port:: 8000 Web port:: 9000 Yacht port:: 8001 arch :: amd64 option :: portainer state :: install extras :: 5.6.5 DNS OK. No portainer containers or images to remove. Pulling and starting portainer/portainer-ce ... 49fce6b461db13d048d040fa348192ee9435ead62988d707660e23356d7c4520 Something went wrong trying to pull and start portainer ... Fait.
-
Thank you to consider my problem.
I've tryed to do it.
At the end off the reinstallation i have :
CodeSuccessfully installed docker. >>> *************** Error *************** communication failure <<< ************************************* >>> *************** Error *************** <<< *************************************
and then i've lost Web GUI and SSH. ping is ok
after reboot : Web Gui is back few seconds , then .. .off
docker is started, my container too, no trace of portainer.
I stoped the container and rebootthen SSH and WebGUI are ok... so it's my container (again, i've got another post about that already, i go to fix it)
well, your solution works, i guess, thanks !! -
can i safely do that : https://docs.docker.com/engine/install/debian/
do i will find the docker items in WebGUI if i try this (clean old version and reinstall) ?
thanks
edit : i tryed sudo apt-get -f install docker , didn't work
-
Hi
Docker doesn't want to start after i did apt-get update and apt-get upgrade. I launched them because i had some network issues , i wanted to test if my NAS reach internet (i fixed it with omv-firstaid)
Now , docker don't start ...
Command journalctl -eu docker
give :
Code
Alles anzeigendéc. 26 14:44:05 bart-nas systemd[1]: Failed to start Docker Application Container Engine. déc. 26 14:44:07 bart-nas systemd[1]: docker.service: Service RestartSec=2s expired, scheduling restart. déc. 26 14:44:07 bart-nas systemd[1]: docker.service: Scheduled restart job, restart counter is at 2. déc. 26 14:44:07 bart-nas systemd[1]: Stopped Docker Application Container Engine. déc. 26 14:44:07 bart-nas systemd[1]: Starting Docker Application Container Engine... déc. 26 14:44:07 bart-nas dockerd[5022]: /usr/bin/dockerd: error while loading shared libraries: /usr/bin/dockerd: unsupported version 0 of Verneed record déc. 26 14:44:07 bart-nas systemd[1]: docker.service: Main process exited, code=exited, status=127/n/a déc. 26 14:44:07 bart-nas systemd[1]: docker.service: Failed with result 'exit-code'. déc. 26 14:44:07 bart-nas systemd[1]: Failed to start Docker Application Container Engine. déc. 26 14:44:09 bart-nas systemd[1]: docker.service: Service RestartSec=2s expired, scheduling restart. déc. 26 14:44:09 bart-nas systemd[1]: docker.service: Scheduled restart job, restart counter is at 3. déc. 26 14:44:09 bart-nas systemd[1]: Stopped Docker Application Container Engine. déc. 26 14:44:09 bart-nas systemd[1]: docker.service: Start request repeated too quickly. déc. 26 14:44:09 bart-nas systemd[1]: docker.service: Failed with result 'exit-code'. déc. 26 14:44:09 bart-nas systemd[1]: Failed to start Docker Application Container Engine.
Thanks for the help
-
sorry ... i just remember i had to clean uses of the shared folder to delete them. They were used in Samba and Rsync ... now, i'm ok , this thread is resolved
-
i've searched on the forum but i didn't find anything can help me, is anyone know how i must do or maybe know a post wich already solved a problem like mine ? thanks
-
my networks problem are fixed now, i just have to fix the shared folders issues and my omv is back online.
To thanks all help i received, i made a little donation -
Hi,
I update my OMV 4 to 5.
All is allmost ok, i remake my mergeFS "dataFS" but now, i have to get back my shared folder and finaly SMB...
When i go in the "shared folder" menu, i got all my old shared folders with N/A as device, so i try to edit it and then , i just have an error message Failed to execute XPath query '//system/fstab/mntent[uuid='ae19cb1d-79e5-444d-a625-9edbb842781c']'.
and in the next screen, in the red part, i can't write back the name of the shared folder. (see screenshot)
i can't delete them neither probably because they are in use (i can't do anything in samba neither)
thanks for the help -
on github someone just told me to put ENABLE_FW = false and it's work, because i don't have any firewall anymore.
That's ok for me so far
Thank you very much for all the help, we can consider this as closed -
thanks for all your answers and the time you spend to try to help me.
I don't understand what you say with " to switch in the OMV UI which IP-tables docker is using and try if this works or" i don't have anything in OMV UI about IP-tables or firewall or i don't find themI'm looking on Github to try to find a help ...
I've find some infos in the container image :
Code
Alles anzeigenenabling firewall Firewall is active and enabled on system startup allowing 51413 through the firewall Skipping adding existing rule allowing 192.168.0.0/24 through the firewall to port 9091 Skipping adding existing rule allowing 192.168.0.0/24 through the firewall to port 22 Skipping adding existing rule allowing 192.168.0.0/24 through the firewall to port 80 Skipping adding existing rule allowing 192.168.0.0/24 through the firewall to port 443 Skipping adding existing rule allowing 192.168.0.0/24 through the firewall to port 9000 Skipping adding existing rule allowing 192.168.0.0/24 through the firewall to port 8000 Skipping adding existing rule allowing 192.168.0.0/24 through the firewall to port 135 Skipping adding existing rule allowing 192.168.0.0/24 through the firewall to port 137 Skipping adding existing rule allowing 192.168.0.0/24 through the firewall to port 138 Skipping adding existing rule allowing 192.168.0.0/24 through the firewall to port 139 Skipping adding existing rule allowing 192.168.0.0/24 through the firewall to port 445 Skipping adding existing rule adding route to local network 192.168.0.0/24 via 192.168.0.1 dev enp3s0 RTNETLINK answers: File exists allowing 192.168.0.0/24 through the firewall to port 9091 Skipping adding existing rule allowing 192.168.0.0/24 through the firewall to port 22 Skipping adding existing rule allowing 192.168.0.0/24 through the firewall to port 80 Skipping adding existing rule allowing 192.168.0.0/24 through the firewall to port 443 Skipping adding existing rule allowing 192.168.0.0/24 through the firewall to port 9000 Skipping adding existing rule allowing 192.168.0.0/24 through the firewall to port 8000 Skipping adding existing rule allowing 192.168.0.0/24 through the firewall to port 135 Skipping adding existing rule allowing 192.168.0.0/24 through the firewall to port 137 Skipping adding existing rule allowing 192.168.0.0/24 through the firewall to port 138 Skipping adding existing rule allowing 192.168.0.0/24 through the firewall to port 139 Skipping adding existing rule allowing 192.168.0.0/24 through the firewall to port 445 Skipping adding existing rule
the thing i don't understand is port 22 (SSH), 80 (web interface) are ok , but not the 9000 (portainer) but in the conf and log , they are the same ... I continue to search, if i find, i'll post here in case someone have the same problem
-
and the end :
Code
Alles anzeigenroot@bart-nas:~# iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy DROP) target prot opt source destination DOCKER-USER all -- anywhere anywhere DOCKER-ISOLATION-STAGE-1 all -- anywhere anywhere ACCEPT all -- anywhere anywhere ctstate RELATED,ESTABLISHED DOCKER all -- anywhere anywhere ACCEPT all -- anywhere anywhere ACCEPT all -- anywhere anywhere Chain OUTPUT (policy ACCEPT) target prot opt source destination Chain DOCKER (1 references) target prot opt source destination ACCEPT tcp -- anywhere 172.17.0.2 tcp dpt:9000 ACCEPT tcp -- anywhere 172.17.0.2 tcp dpt:8000 Chain DOCKER-ISOLATION-STAGE-1 (1 references) target prot opt source destination DOCKER-ISOLATION-STAGE-2 all -- anywhere anywhere RETURN all -- anywhere anywhere Chain DOCKER-ISOLATION-STAGE-2 (1 references) target prot opt source destination DROP all -- anywhere anywhere RETURN all -- anywhere anywhere Chain DOCKER-USER (1 references) target prot opt source destination RETURN all -- anywhere anywhere # Warning: iptables-legacy tables present, use iptables-legacy to see them
-
Code
Alles anzeigenChain ufw-track-output (1 references) target prot opt source destination ACCEPT tcp -- anywhere anywhere ctstate NEW ACCEPT udp -- anywhere anywhere ctstate NEW Chain ufw-user-forward (1 references) target prot opt source destination Chain ufw-user-input (1 references) target prot opt source destination ACCEPT tcp -- anywhere anywhere tcp dpt:51413 ACCEPT udp -- anywhere anywhere udp dpt:51413 ACCEPT tcp -- 192.168.0.0/24 anywhere tcp dpt:9091 ACCEPT udp -- 192.168.0.0/24 anywhere udp dpt:9091 ACCEPT tcp -- 192.168.0.0/24 anywhere tcp dpt:ssh ACCEPT udp -- 192.168.0.0/24 anywhere udp dpt:22 ACCEPT tcp -- 192.168.0.0/24 anywhere tcp dpt:http ACCEPT udp -- 192.168.0.0/24 anywhere udp dpt:80 ACCEPT tcp -- 192.168.0.0/24 anywhere tcp dpt:https ACCEPT udp -- 192.168.0.0/24 anywhere udp dpt:443 ACCEPT tcp -- 192.168.0.0/24 anywhere tcp dpt:9000 ACCEPT udp -- 192.168.0.0/24 anywhere udp dpt:9000 ACCEPT tcp -- 192.168.0.0/24 anywhere tcp dpt:8000 ACCEPT udp -- 192.168.0.0/24 anywhere udp dpt:8000 ACCEPT tcp -- 192.168.0.0/24 anywhere tcp dpt:epmap ACCEPT udp -- 192.168.0.0/24 anywhere udp dpt:epmap ACCEPT tcp -- 192.168.0.0/24 anywhere tcp dpt:netbios-ns ACCEPT udp -- 192.168.0.0/24 anywhere udp dpt:netbios-ns ACCEPT tcp -- 192.168.0.0/24 anywhere tcp dpt:netbios-dgm ACCEPT udp -- 192.168.0.0/24 anywhere udp dpt:netbios-dgm ACCEPT tcp -- 192.168.0.0/24 anywhere tcp dpt:netbios-ssn ACCEPT udp -- 192.168.0.0/24 anywhere udp dpt:netbios-ssn ACCEPT tcp -- 192.168.0.0/24 anywhere tcp dpt:microsoft-ds ACCEPT udp -- 192.168.0.0/24 anywhere udp dpt:microsoft-ds Chain ufw-user-limit (0 references) target prot opt source destination LOG all -- anywhere anywhere limit: avg 3/min burst 5 LOG level warning prefix "[UFW LIMIT BLOCK] " REJECT all -- anywhere anywhere reject-with icmp-port-unreachable Chain ufw-user-limit-accept (0 references) target prot opt source destination ACCEPT all -- anywhere anywhere Chain ufw-user-logging-forward (0 references) target prot opt source destination Chain ufw-user-logging-input (0 references) target prot opt source destination Chain ufw-user-logging-output (0 references) target prot opt source destination Chain ufw-user-output (1 references) target prot opt source destination