zot/examples/config-s3.json

{
    "distSpecVersion": "1.0.1-dev",
    "storage": {
        "rootDirectory": "/tmp/zot",
        "dedupe": true,
        "storageDriver": {
            "name": "s3",
            "rootdirectory": "/zot",
            "region": "us-east-2",
            "bucket": "zot-storage",
            "secure": true,
            "skipverify": false
        },
        "subPaths": {
            "/a": {
                "rootDirectory": "/tmp/zot1",
                "dedupe": false,
                "storageDriver": {
                    "name": "s3",
                    "rootdirectory": "/zot-a",
                    "region": "us-east-2",
                    "bucket": "zot-storage",
                    "secure": true,
                    "skipverify": false
                }
            },
            "/b": {
                "rootDirectory": "/tmp/zot2",
                "dedupe": true,
                "storageDriver": {
                    "name": "s3",
                    "rootdirectory": "/zot-b",
                    "region": "us-east-2",
                    "bucket": "zot-storage",
                    "secure": true,
                    "skipverify": false
                }
            },
            "/c": {
                "rootDirectory": "/tmp/zot3",
                "dedupe": true,
                "storageDriver": {
                    "name": "s3",
                    "rootdirectory": "/zot-c",
                    "region": "us-east-2",
                    "bucket": "zot-storage",
                    "secure": false,
                    "skipverify": false
                }
            }
        }
    },
    "http": {
        "address": "127.0.0.1",
        "port": "8080"
    },
    "log": {
        "level": "debug"
    }
}
storage: add s3 backend support (without GC and dedupe) Signed-off-by: Petu Eusebiu <peusebiu@cisco.com> 2021-07-16 22:53:05 -05:00			`{`
ext: use distribution spec route prefix for extension api Following the spec defined here https://github.com/opencontainers/distribution-spec/tree/main/extensions Signed-off-by: Shivam Mishra <shimish2@cisco.com> 2022-02-24 15:31:36 -05:00			`"distSpecVersion": "1.0.1-dev",`
storage: add s3 backend support (without GC and dedupe) Signed-off-by: Petu Eusebiu <peusebiu@cisco.com> 2021-07-16 22:53:05 -05:00			`"storage": {`
s3: added logic for deduping blobs Because s3 doesn't support hard links we store duplicated blobs as empty files. When the original blob is deleted its content is moved to the the next duplicated blob and so on. Signed-off-by: Petu Eusebiu <peusebiu@cisco.com> 2022-04-12 05:01:04 -05:00			`"rootDirectory": "/tmp/zot",`
			`"dedupe": true,`
storage: add s3 backend support (without GC and dedupe) Signed-off-by: Petu Eusebiu <peusebiu@cisco.com> 2021-07-16 22:53:05 -05:00			`"storageDriver": {`
			`"name": "s3",`
s3: added logic for deduping blobs Because s3 doesn't support hard links we store duplicated blobs as empty files. When the original blob is deleted its content is moved to the the next duplicated blob and so on. Signed-off-by: Petu Eusebiu <peusebiu@cisco.com> 2022-04-12 05:01:04 -05:00			`"rootdirectory": "/zot",`
storage: add s3 backend support (without GC and dedupe) Signed-off-by: Petu Eusebiu <peusebiu@cisco.com> 2021-07-16 22:53:05 -05:00			`"region": "us-east-2",`
			`"bucket": "zot-storage",`
			`"secure": true,`
			`"skipverify": false`
			`},`
			`"subPaths": {`
			`"/a": {`
s3: added logic for deduping blobs Because s3 doesn't support hard links we store duplicated blobs as empty files. When the original blob is deleted its content is moved to the the next duplicated blob and so on. Signed-off-by: Petu Eusebiu <peusebiu@cisco.com> 2022-04-12 05:01:04 -05:00			`"rootDirectory": "/tmp/zot1",`
			`"dedupe": false,`
storage: add s3 backend support (without GC and dedupe) Signed-off-by: Petu Eusebiu <peusebiu@cisco.com> 2021-07-16 22:53:05 -05:00			`"storageDriver": {`
			`"name": "s3",`
s3: added logic for deduping blobs Because s3 doesn't support hard links we store duplicated blobs as empty files. When the original blob is deleted its content is moved to the the next duplicated blob and so on. Signed-off-by: Petu Eusebiu <peusebiu@cisco.com> 2022-04-12 05:01:04 -05:00			`"rootdirectory": "/zot-a",`
storage: add s3 backend support (without GC and dedupe) Signed-off-by: Petu Eusebiu <peusebiu@cisco.com> 2021-07-16 22:53:05 -05:00			`"region": "us-east-2",`
			`"bucket": "zot-storage",`
			`"secure": true,`
			`"skipverify": false`
			`}`
			`},`
			`"/b": {`
s3: added logic for deduping blobs Because s3 doesn't support hard links we store duplicated blobs as empty files. When the original blob is deleted its content is moved to the the next duplicated blob and so on. Signed-off-by: Petu Eusebiu <peusebiu@cisco.com> 2022-04-12 05:01:04 -05:00			`"rootDirectory": "/tmp/zot2",`
			`"dedupe": true,`
storage: add s3 backend support (without GC and dedupe) Signed-off-by: Petu Eusebiu <peusebiu@cisco.com> 2021-07-16 22:53:05 -05:00			`"storageDriver": {`
			`"name": "s3",`
s3: added logic for deduping blobs Because s3 doesn't support hard links we store duplicated blobs as empty files. When the original blob is deleted its content is moved to the the next duplicated blob and so on. Signed-off-by: Petu Eusebiu <peusebiu@cisco.com> 2022-04-12 05:01:04 -05:00			`"rootdirectory": "/zot-b",`
storage: add s3 backend support (without GC and dedupe) Signed-off-by: Petu Eusebiu <peusebiu@cisco.com> 2021-07-16 22:53:05 -05:00			`"region": "us-east-2",`
			`"bucket": "zot-storage",`
			`"secure": true,`
			`"skipverify": false`
			`}`
			`},`
			`"/c": {`
s3: added logic for deduping blobs Because s3 doesn't support hard links we store duplicated blobs as empty files. When the original blob is deleted its content is moved to the the next duplicated blob and so on. Signed-off-by: Petu Eusebiu <peusebiu@cisco.com> 2022-04-12 05:01:04 -05:00			`"rootDirectory": "/tmp/zot3",`
			`"dedupe": true,`
storage: add s3 backend support (without GC and dedupe) Signed-off-by: Petu Eusebiu <peusebiu@cisco.com> 2021-07-16 22:53:05 -05:00			`"storageDriver": {`
			`"name": "s3",`
s3: added logic for deduping blobs Because s3 doesn't support hard links we store duplicated blobs as empty files. When the original blob is deleted its content is moved to the the next duplicated blob and so on. Signed-off-by: Petu Eusebiu <peusebiu@cisco.com> 2022-04-12 05:01:04 -05:00			`"rootdirectory": "/zot-c",`
storage: add s3 backend support (without GC and dedupe) Signed-off-by: Petu Eusebiu <peusebiu@cisco.com> 2021-07-16 22:53:05 -05:00			`"region": "us-east-2",`
			`"bucket": "zot-storage",`
			`"secure": false,`
			`"skipverify": false`
			`}`
			`}`
			`}`
			`},`
			`"http": {`
			`"address": "127.0.0.1",`
Remove AllowReadOnly and ReadOnly Signed-off-by: Nicol Draghici <idraghic@cisco.com> Remove check and set header every time Signed-off-by: Nicol Draghici <idraghic@cisco.com> 2022-07-14 10:13:46 -05:00			`"port": "8080"`
storage: add s3 backend support (without GC and dedupe) Signed-off-by: Petu Eusebiu <peusebiu@cisco.com> 2021-07-16 22:53:05 -05:00			`},`
			`"log": {`
			`"level": "debug"`
			`}`
			`}`