Need documentation on structure of S3MOCK_DATA_DIR

[schechi1190]

I am looking to use the s3mock server in the docket container with existing content. I have a directory with files I need in the bucket. I am not clear how I should organize the files so that they are loaded as is into a bucket. I am starting the docker like this:

docker run -p 8001:8001 -v D:\AWS\upload:/tmp/s3mock/ -e "S3MOCK_DATA_DIR=/tmp/s3mock" findify/s3mock:latest

How am I supposed to create a bucket and create keys pointing to data under D:\AWS\upload? Is it how it is supposed to be used?

[sebastiandaberdaku]

I think that s3mock is ignoring the environment variable. When I use a similar command, when accessing the docker container interactively, I noticed that there are always two s3mock folders in the tmp directory, the second one followed by many digits:
root@868d4485d245:/tmp# ls
hsperfdata_root s3mock s3mock17442364732684116532

The new buckets are always created inside s3mock17442364732684116532 and not s3mock. The problem is these the digits seem to be randomly created from time to time.

[kriegster108]

defintely a blocker for me I am at the same exactly isuse. How can i preload data when the bucket folder generation cant be controlled?