Not really. I also didn't have much data in them, so I opted to start from scratch. I'd recomend searching for "service docker" to find how to run that thing in dockers compose. Then I make a folder for each thing. In my home directory, I make a new folder. Say fileBrowser. Then inside that I make docker-compose.yml and put the compose from the internet (if you find a docker run, you can convert it to compose via sites like composerizer). Then for config volumes I like to specify ./ so it goes to the current folder. I.e. ./filebrowserconfig/settings.json:/settings.json so that inside the fileBrowser folder we're already in, it has a folder called filebrowserconfig and a file called settings.json. (note that docker tries to make folders, not files. So if the json file doesn't already exist, it'll make a folder named settings.json lol)