Portainer Agent = lost data?

[rovingclimber]

Ask a Question!

I've searched several times over a while to see whether it's just me being stupid ... but does anyone else have issue with losing data when working with a docker instance connected via agent?

I'll be more specific.

For example if you have portainer_ce running in a docker instance and you build a new image using the web editor, that dockerfile ends up in a folder on that host that's mapped (eg portainer_data:/data).

When you do the same thing on a remote docker instance via portainer agent, your dockerfile doesn't go into the same folder on the portainer instance, so presumably is saved somewhere in the portainer agent image. However we don't seem to have the same option to map a volume to /data to be able to get at it, it's stuck inside that image somewhere.

I just spent a while building an image that way, got it running as I wanted, but then realised I'd navigated away from the web editor and I no longer can see the dockerfile I was working on, and I am struggling to find a way in to the portainer agent image to find it. I've had similar issues in the past around stacks when performing agent upgrades, it loses all the stack config because, again, it seems to be inside the agent image.

Has anyone else had the same issues? Did you find some solution? Am I being incredibly stupid or is this a bit of a design oversight in the way the agent works?