4 ms·
Agree 100%. Running containers on AWS requires uploading an image to a registry/repository, but there isn't any API to actually upload the .json manifest files
by chriswarbo 5y ago
Agree 100%.
Running containers on AWS requires uploading an image to a registry/repository, but there isn't any API to actually upload the .json manifest files and .tar.gz layer files they need, even if I have them sat in a folder in front of me (compare this to Lambda, where we can upload a .zip to S3).
The worst part is that the "official" way to upload artifacts to a repository actually requires installing the 'docker' command, running some sort of "login" command in that, piping around some secret tokens generated by the AWS CLI, etc.
The only other approach I could find is their "low level" chunk-based upload API. I wrote a Python script around that (pretty much just a 'while' loop), so I can avoid this docker sillyness.
https://docs.aws.amazon.com/AmazonECR/latest/userguide/getting-started-cli.html https://docs.aws.amazon.com/AmazonECR/latest/userguide/getti...
- Nullabillity 5y agoLooks like Docker's registry API (what the docker CLI uses) supports doing single-chunk uploads: https://docs.docker.com/registry/spec/api/#monolithic-upload https://docs.docker.com/registry/spec/api/#monolithic-upload.
- chriswarbo 5y agoI think accessing AWS's Docker API is what requires the "fake login dance" to begin with.
- Nullabillity 5y agoYeah, but "fake login dance" is mostly just a consequence of the Docker CLI's design. As an API client you just get an API credential and use it to authenticate against the API.