search

pi-node / instructions

255 stars 154 forks source link

Pi Node 4.11 doesn't recognize Docker desktop #356

Open shkdjsy opened 4 months ago

shkdjsy commented 4 months ago

when I turn on the node, stellar-dummy runs. No pi consensus starts pi node

How to solve this?

remzicirit commented 4 months ago

I had same problem in teh past just remove docker and reinstall it solved the problem

shkdjsy commented 4 months ago

I had same problem in teh past just remove docker and reinstall it solved the problem

I did many times. remove and reinstall both docker and pi node.

I only happen in this 4.11 version, any other version has this issue

NET6666STREEM commented 4 months ago

It seems all I am having is issues

Rockman1955 commented 4 months ago

Same issues and same steps to correct, and still not showing he Pi-Consensus Container

Please revise as to what happen in the Update?

Thanks in advance

Rockman1955 commented 4 months ago

when I turn on the node, stellar-dummy runs. No pi consensus starts pi node

How to solve this?

Please update us all, and I will also if/we find the fix to the issue...

TIA

Rockman1955 commented 4 months ago

when I turn on the node, stellar-dummy runs. No pi consensus starts pi node

How to solve this?

Any Update or Fix to this Issues???

openet001 commented 4 months ago

same with issue 359 . tried to downgrade to pi node 0.4.7 , upgrade pi node 0.4.9 , pi node 0.4.11 are all ok. But upgrade to pi node 0.4.11, it seems the bugs occurd again.

Rockman1955 commented 4 months ago

same with issue 359 . tried to downgrade to pi node 0.4.7 , upgrade pi node 0.4.9 , pi node 0.4.11 are all ok. But upgrade to pi node 0.4.11, it seems the bugs occurs again.

Yes same here, I uninstalled the 0.411 and re-installed the 0.49, But when the 0.49 started, it then gave the message 'A new Version Is Available", and Pi Node will restart and install the new 0.411,

So back to where the 0.411 is not loading the Pi-Consensus Container....

Any other fix to this Issues??

pabaldomar commented 4 months ago

Same issue with macOs.

NET6666STREEM commented 4 months ago

Some machines don't have a virtual machine if you have a virtual machine make sure it's not connected to your system itself have it running off of your system like subsystem and make sure it's not connected to your PC whatsoever then when you run it install doctor within it I don't know if you would have to do pi node within it though I'm still trying to learn as much as I can before I start really doing my work and I have a lot of accumulated but it's going to give me a lot to do and I will have the time to do it so if anybody wants to get a head start be obliged but tag me in it thank you

NET6666STREEM commented 4 months ago

It's because of the point of like they told me I had to make another account use my link as far as my recommendation code for that account make sure it's me everything's correct just like the first one because of something I don't know but that is also for imaging examples learning purposes etc that will be figured out once main net is open net so any pie that I am accumulating within the other account only on this circumstance issued permission by CoreTeem Those are only circumstances that you should ever make another account you should never ever make another account only if you are an ambassador developer I repeat only if you are a ambassador developer thank you what I mentioned above doesn't apply to you then it doesn't apply to you okay no duplicate accounts unless ordered bye licensed Core Teem

nhatvhm commented 2 months ago

Same issue with macOs.

Everything is automatically after you have done installation Pi Node v0.4.11 and Docker v4.31.0 on MacOS Monterey 12.7.5 Note: Please select configuration your Pi Node is not master if you don't have Port forwarding opening.

This is my Pi Node on Mac OS which my configuration is not master and still have Node bonus. GRtxxRubgAAiahA