Adding --properties arguments when running docker image

[pancochea]

We want to add arguments to add two properties files to s3, locally, we run it this way:

s3proxy --properties "/etc/s3proxy/file1" --properties "/etc/s3proxy/file2"

Now we want to run it in kubernetes, so we created a deployment and added args to the pod:

spec:
  containers:
    - args:
        - '--properties'
        - /etc/s3proxy/file1
        - '--properties'
        - /etc/s3proxy/file2

But the properties are not being loaded. After checking the dockerfile and the script, I can see that arguments are not being passed to the exec command, so it's not going to load those arguments.

Is there a way to load those properties, or we will have to custom build s3proxy?

Also, we don't understand the --properties /dev/null at the end of the exec.

[gaul]

Can you explain your use case more? S3Proxy only accepts one parameters file. I don't remember all the choices I made 10 years ago but I believe it was common at that time to configure Docker containers via environment variables due to poor bind mount support. If it is more common to configure via files now I would happily merge support. Can you investigate this?

[pancochea]

You can stack properties to S3Proxy by running the first command you see in the issue:

s3proxy --properties "/etc/s3proxy/file1" --properties "/etc/s3proxy/file2"
What we are trying to achieve here it's to have a single point for different backends (what a proxy is expected to do). We have a bucket in Minio, and the rest in S3, but we want the access to be a single access point from the application point of view.

We managed to make it work by changing your base image to accept more properties as stated.