Posts by SinE

Quote from 88765432536

Why? did you not the this thread about not needing that junk?

Hi, thanks for comment... 🤔

I'm happy with Portainer-CE. 😇

Quote from BernH

Your zombie is an old container with a different name that never got cleaned up. simply remove/delete the old container from the containers tab and then try the prune functions to get any residue.

Contrary to some other comments in this threat, I don't think protainer is garbage. It is quite good if you need the extra functionality it provides, and I was using it myself until a couple of weeks ago when it got crippled with some api version issues.

This kind of thing will not happen with the built in compose plugin, which as I said, will do everything the vast majority of users need.

If like me, you are not a lover of the compose plugin's "look and feel" and/or need some remote docker admin functions, Arcane is a nice alternative, which is what I switched to myself when portainer had the api issues.

Just like with portainer though, it is a container to manage containers so there us an added layer of complexity, while the compose plugin is straight docker.

Display More

In my case it was a a Zombie that I was scare to delete until the new Portainer-CE started to run properly.

As you, I don't like Compose.

About Arcane I will try it, thanks for your recomendation!

Hi Team,

I had this issue today after an update.

Finally I was able to run Portainer again.

You are right about to remove the old Portainer, but I had issues with the "name" and the "port", here my final confoguration:

services:
portainer:
image: portainer/portainer-ce:latest 
container_name: portainer-ce
restart: unless-stopped
security_opt:
- no-new-privileges:true
volumes:
- /etc/localtime:/etc/localtime:ro
- /var/run/docker.sock:/var/run/docker.sock:ro
- ./data:/data
ports:
- 9443:9443

After this configuration and "UP" the new portainer i can see the "zombie"...

Regards

Today, afte some weeks from migrte the system from OMV to OMV7, is the first time that appear this message in my main computer.

Direct translation:

[KB2933] ARP, DNS or ICMP cache poisoning attack

The IP that is "doing" this action, is the OMV7 IP...

My antivirus is NOD32.

Someone had have the same message?

Quote from chente

It's strange to limit the server choice to such a small region. This restricts to a minimum the possibilities offered by the globalized world in which we live. As you say, you're free to choose what you want, but don't be surprised if it doesn't work.

I assumed that all server should have the same revision/version. But.... no.

Quote from chente

For some special reason?

🙄 I felt free to choose the server...

Quote from crashtest

Out of curiosity, what server were you using before?

One from Catalonia, now I don't remember what ot them.

The first that appears with the domain .cat.

Regards

The "issue" is not that the stream is slow, only that the info in OMV/Portainer is not real. 😅

Thanks!

Today I was fighting to run a fresh OMV7.

All is working as with the previous versions, but today I check one value abput the CPU consumption un Docker, and what was my surprise when...

OMV Info:

Portainer Info:

The server Runs normaly, with any delay

When a video file is running, the CPU usage arrives at +365%.

If I run 2 Videos from diferent devices at the same Time, also the CPU usage is high, but no delay is detected..

Maybe there is a bug about the real values?

For my personal use it is not a "problem", until the sistem works properlly.

My Hardware:

The image also is with 2 Videos running at the same time

regards

If this matter reamains open...

Same issue, fresh install with no Samba Acces.

I used a local server repositories in my 1st installation. Issues that I was not able to fix after 2h

I did a new fresh install, but using the default debian server to donwload updates... and maaaaagic was done.

regards

Quote from votdev

Run dpkg --configure -a as suggested by the error messages.

Yes, I did, and I also told in my oprevious comment

regards!

Quote from SinE

Done!

Updates thru webgui... shoed this error... but appli manually the recommended instruction, seems that it world properly

Quote from chente

With any update on any operating system there is a small risk of something going wrong. That is why it is convenient to have backups. In the worst case, you can always go back.

Staying on an outdated version is not a good idea.

Done!

Quote from votdev

The version you are running is very very old, so consider to upgrade now

No issues with the last updates?

Thnks!

I want to update my server... do you think now is a good idea? or not...

Actual Version: 6.0.24-1 (Shaitan)

After read your inputs... I will wait a week... 😣Before updat my OMV,

Quote from raulfg3

works for me, perhaps some DNS problem in your side?

https://hub.docker.com/r/linuxserver/jellyfin

As I will not use miniDLNA, I disabled it. best solution for me

Hi Team,

The Jellyfin Server (from LinuxServer .io) seems dead, the error message when I tried to deploy the container is:

Failure

Request failed with status code 500

I was not able to find any diagnostic but I rememember that last time, I activated the MiniDLNA server under OMV6, when I dissable this MiniDLNA Server, the Jellyfin Server starts to run again with no issues.

Regards! Hope it helps to other users, or just a rimender for me when I will do the same fault.

Finallly I decided to update my server to work under SSDs and with the last Version 6.

1st day, all was fine with Portainer.

2nd day, Portainer was not able to Pull images , showing this error:

- Get "https://registry-1.docker.io/v2/": dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:51536->[::1]:53: read: connection refused

I decided to reinstall Portainer, but it retuned me a DNS error.

Solution: that I find also in other threat about OMV5, was to put a manual DNS server in my ethernet device, for example: 8.8.8.8

Now, all seems to be alive.

wow, I'm working woth version 5 for a long time, and I'm thinking aldo to migrate the system to the new release 6... but with a fresh installation.

The system is working in a little Nuk, with an Intel Pentium J4205 1.50Ghz with 8Gb RAM, where I'm running a some Dockers (JellyFin, NoIp, Transmisssion, and something else) and a Sharefile system, and it works fine for me, I assume that it will be enought to run the same configuration with version 6.... Happy to read that OMW Extras still alive for version 6.

Shinobi, waiting you comments about if your update will be success!!!