Replies: 4 comments 3 replies
-
|
Hey @mhokama86 — thanks for the writeup. Without the actual error my best guess is one of two things, and both are install-side sharp edges I need to file down: 1. If you used Portainer's "Web editor" or "Upload" mode for the stack: the compose file currently has 2. About the A few other Portainer gotchas worth flagging while I'm at it:
If you try Repository mode + leave the named volumes alone and you're still hitting errors, paste the error from Portainer's stack logs (or the failing container's logs) and I'll dig in directly. On the one-liner installer: not yet, but it's on the roadmap. The same compose hygiene that would make Portainer painless is also what unblocks a Appreciate the discussion. This is exactly the kind of feedback that helps me sand the rough edges, so genuinely thank you for taking the time. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the clean baseline — that error message tells me exactly what's going on. The error: The fix — use Repository mode:
What this changes: Portainer clones the repo into One important heads-up before anything else: the Two other things you'll likely hit after the build succeeds:
On the bigger picture: the build-from-source thing you hit is the #1 reason Portainer Stacks isn't smooth for FilaOps right now. The fix is publishing prebuilt images to GitHub Container Registry so Portainer can pull them directly instead of building — that's queued for after the current launch work, alongside a proper Portainer guide and a one-line installer. You hitting this is exactly the forcing function I needed to prioritize it. Give Repository mode a try and let me know how it goes. If the build itself fails (vs. the context-not-found error), paste the build logs from Portainer's stack view and I'll dig in. |
Beta Was this translation helpful? Give feedback.
-
|
<img width="1318" height="369" alt="image" src="https://github.com/user-attachments/assets/041565d4-9aca-499c-96fa-7dec52d0f155" shows sucessfully deployed, but here's the status of the containers. |
Beta Was this translation helpful? Give feedback.
-
Woooowhooo! got it running in a dev environment!
|
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
do you have info to deploy via portainer. i tried with the docker-compose and env variables, update the volume to a ./ and still getting errors. anything you could do would help.
if not, do you have a one line installer guide?
Beta Was this translation helpful? Give feedback.
All reactions