OpenMediaVault Docker OctoPrint path?

Get Help Docker
1

Just installed OctoPrint on my Pi3B+ which runs OpenMediaVault.

Installed in a Docker Container, and the UI appears correct, I can upload files, etc.

I also have the ArcWelder Plug-in active.

I am wanting to find the location, on the Pi, where the Uploaded ( and converted ArcWelder ) files are stored.

The OctoPrint settings show the Folders for Uploads as
/root/.octoprint/uploads

If I 'test' the path in OP Settings, it displays that the path is valid.

but I can not find this location when I ssh to the Pi using Putty

2

That's because the path in OctoPrint is relative to the container root, so you need to go looking for the location the container is mounted to the filesystem.

1 Like
3

Thanks Charlie. I just found it.
Now to make it a shared folder so I can access it from the Win PC as a network drive

4

The path is :
mnt/fs/var/lib/docker/volumes/24df5eb6e72a2df7c5bd64b27760ff6a83b0d3b5bbb8157734c23090adcbb252/_data/uploads/

when I create a Shared Folder, then go to SMB/CIFS and add the folder as a share, I can map ( on my Win PC ) to the shared folder, but it is empty.

Have I shared the incorrect path / syntax error ?

If I go to the path in Cloud Commander, I can see the 2 files that are in the folder

5

Moved the topic to #support:docker and tagging @LongLiveCHIEF since he's the one with the docker brain around here. I'm still learning :slightly_smiling_face:

6

Thank You Charlie

1 Like
7

Do not upload manually into the uploads folder, the watched folder is what you are supposed to use.

8

I do not want to upload to the folder. I want to automate a download of the converted file created by ArcWelder, so I can verify that the print will look as expected, before starting the print

9

There is also a console version of the arcwelder pre-processor here. You can find the latest release binaries here, though I'm not 100% sure all of the OS builds are working 100%. It can be added to most slicers pretty easilly. What OS are you using to slice?

FYI, I'll be pushing another update soon to handle an issue caused by offsetting X and Y via a g92 command.