Files are saved as folders containing xl.meta files for minio docker container

[TheSharpOwl]

Describe the bug

When uploading a file (image png/jpg or json file) using a string stream, let's say sample.json I get a folder called sample.json and inside of it there is xl.meta file.

I tried to save the image locally and it was working totally okay so the encoder code is working. Also, I remember one year ago it was saving on minio container fine but now I came back to the same exact code one year ago but still the issue arises.

Also it was discussed in github on AWS C++ sdk repo here

Conditions:

• Docker image for minio to connect to

Where it was tried:

• Ubuntu 18
• Windows 10

How it can be seen

• Using a terminal and trying to cd the image name
• Using volumes mounting

Expected Behavior

Get an image/json file not a folder

Current Behavior

I get a folder called sample.png and inside of it there is xl.meta file.

Reproduction Steps

docker image command line:

docker run -p 9000:9000 --name minio  -e "MINIO_ACCESS_KEY=minioadmin" -e "MINIO_SECRET_KEY=miniokey" -v C:/aws/data:/data  minio/minio server /data

// connect to a bucket using the examples then using this method:
bool saveData(const char *rawData,
                           size_t dataSize,
                           const std::string &filename) {
  Aws::S3::Model::PutObjectRequest putObjectRequest;
  putObjectRequest.WithBucket(bucketName_.c_str()).WithKey(filename.c_str());

  auto data = Aws::MakeShared<Aws::StringStream>(
      "PutObjectInputStream",
      std::stringstream::in | std::stringstream::out
          | std::stringstream::binary);

  data->write(rawData, dataSize);

  putObjectRequest.SetBody(data);
   // these lines were tried too and they didn't fix it
  // putObjectRequest.SetContentType("image/jpeg");
  // putObjectRequest.SetContentLength(dataSize);
  auto result = client_->PutObject(putObjectRequest);
  if (result.IsSuccess()) {
    return true;
  }
  return false;
}

Full code repo link (to reproduce the issue with commands for docker file in readme)

AWS CPP SDK version used

1.11.65 (vcpkg)

Compiler and Version used

Visual Studio 2017 15.9.48 Community

Operating System and version

Windows 10 19044.3086

[klauspost]

This is expected behavior. You cannot and should not access files outside the S3 API.

[klauspost]

MinIO provides an S3 API which allows full control of your objects. Use that for all operations.

There are many clients, including our own: mc.

[TheSharpOwl]

Thank you very much it works now for me now )

[umerasghar-ibm]

Hi @TheSharpOwl , how you were able to fix this issue? can you guide pleas.e

[TheSharpOwl]

@umerasghar-ibm You should use this to copy the files (using this executable commands, you can copy the files or check them)

[lakuhana]

MinIO provides an S3 API which allows full control of your objects. Use that for all operations.
There are many clients, including our own: mc.

I would like the developer to provide a configuration that lets me choose between using 'xl.meta' or my own file

[kisst]

While I understand the fact that the underlying storage of objects is not designed for direct access I see a valid use case for it. I can imagine a simple, lightweight Fuse based solution for at least read only mounts, even with the tradeoff of having no event triggers nor permission management.

[harshavardhana]

Sure feel free to work on it, let us know if you need any guidance.

[lakuhana]

有很多客户，包括我们自己的客户：mc。
I would like the developer to provide a configuration that lets me choose between using 'xl.meta' or my own file

[klauspost]

That is not going to happen.