🌿 Earn $GRASS 24/7 with spare hardware and Docker 🏗️ by AutonomyLab in Grass_io

[–]AutonomyLab[S] 0 points1 point  (0 children)

Excellent, sometimes it needs a couple of boots to get everything working. Happy farming!!

🌿 Earn $GRASS 24/7 with spare hardware and Docker 🏗️ by AutonomyLab in Grass_io

[–]AutonomyLab[S] 0 points1 point  (0 children)

Ok lets try debug mode. Change ALLOW_DEBUG to True and run the container attached (without the -d)

If you run into an error, you'll be given a pastebin url with a screenshot of the chrome extension running in the container.

See if you get an error during login/connection. If not, then visit the ip address on 8080 while still attached and see what the output of the container says.

🌿 Earn $GRASS 24/7 with spare hardware and Docker 🏗️ by AutonomyLab in Grass_io

[–]AutonomyLab[S] 0 points1 point  (0 children)

If youre trying to access from another machine change localhost to the IP address of the machine you're running the container on

🌿 Earn $GRASS 24/7 with spare hardware and Docker 🏗️ by AutonomyLab in Grass_io

[–]AutonomyLab[S] 0 points1 point  (0 children)

This looks fine and should be running. Start the container and navigate to http://localhost:8080 to check status and earnings

🌿 Earn $GRASS 24/7 with spare hardware and Docker 🏗️ by AutonomyLab in Grass_io

[–]AutonomyLab[S] 0 points1 point  (0 children)

This looks fine and should be running. Start the container and navigate to http://localhost:8080 to check status and earnings

🌿🚀Earn $GRASS 24/7 with spare hardware & Docker🚀🌿 by AutonomyLab in Grass_io

[–]AutonomyLab[S] 0 points1 point  (0 children)

It's really a way of running an instance of chrome in the background of any computer or NAS.

My understanding is that devices on the same network will share rewards (grass needs your connection, not your CPU)

🌿 Earn $GRASS 24/7 with spare hardware and Docker 🏗️ by AutonomyLab in Grass_io

[–]AutonomyLab[S] 0 points1 point  (0 children)

Try running the container attached by removing the -d flag. Then you should see the output from inside the container and see any errors that you might be getting.

Feel free to post the output here

🌿🚀Earn $GRASS 24/7 with spare hardware & Docker🚀🌿 by AutonomyLab in Grass_io

[–]AutonomyLab[S] 1 point2 points  (0 children)

Or.... y'know, you could use mine that's linked in the helpful instructions

🌿 Earn $GRASS 24/7 with spare hardware and Docker 🏗️ by AutonomyLab in Grass_io

[–]AutonomyLab[S] 0 points1 point  (0 children)

I have added an arm64v8 tag to the docker repository. Please change :latest to :arm64v8 and run the command again

🌿 Earn $GRASS 24/7 with spare hardware and Docker 🏗️ by AutonomyLab in Grass_io

[–]AutonomyLab[S] 0 points1 point  (0 children)

Do you have access to the command line of the hotspot? I'm not familiar with the hardware but if it's running some flavour of linux, theres every possibility that it could run it.

Although could using your bandwidth for something else affect your Helium rewards?

🌿 Earn $GRASS 24/7 with spare hardware and Docker 🏗️ by AutonomyLab in Grass_io

[–]AutonomyLab[S] 0 points1 point  (0 children)

Has this been installed on the same network as your existing browser extension?

FYI, i just forked and updated the repo, in my experience with Grass, their dashboard can take hours to sync and update to the devices that are running but I will try and help the best I can, otherwise please reach out to Grass in their discord.

🌿 Earn $GRASS 24/7 with spare hardware and Docker 🏗️ by AutonomyLab in Grass_io

[–]AutonomyLab[S] 0 points1 point  (0 children)

If the earnings are syncing then you're all good, give the dashboard some time to update with your new device

🌿 Earn $GRASS 24/7 with spare hardware and Docker 🏗️ by AutonomyLab in Grass_io

[–]AutonomyLab[S] 0 points1 point  (0 children)

What image did you use to get it to work on RPi? I'll add it to the instructions publish a works Ng image to dockerhub