在Docker容器中更新一个大文件

huangapple go评论60阅读模式
英文:

Updating a large file in a Docker container

问题

目前我有一组应用程序运行在不同的Docker容器中。这些容器本身运行在云上。有时需要进行配置更新。配置更新需要我发送一个大小为300 - 500 MB的文件。我想知道最佳做法是什么。

这些容器每个都有一个公开的Swagger文档,所以我可以公开一个端点来加载文件。在这种情况下,我应该通过请求正文发送文件的内容吗?

英文:

I currently have a set of applications running in separate Docker containers. The containers themselves are running on the Cloud. Sometimes, a configuration update is necessary. The configuration update requires me to send a file that is 300 - 500 MB in size. I am wondering what would be the best practice to do this.

The containers each have a Swagger doc exposed, so I could expose an endpoint to potentially load the file in. Would I send the contents of the files via the request body in this case?

答案1

得分: 3

I do not think exposing an endpoint and uploading an entire file to the server is a great idea both due to Network and Security issues.

Currently, I do not have any idea about what those update files are, but by your approach container will be doing double work. (Doing its own job + downloading updates)

For copying the updated files you use a secure protocol like scp from local to the docker container. now assuming you have backups of update files in case of network failure while copying updates then this approach works.

Here is a little better strategy.

  1. Ideally all your update files should be hosted on docker host which is then mounted using volume to docker container

  2. Better way will be you should upload this update file to a cloud storage service that is highly scalable.

  3. Your storage trigger will hit an endpoint which will start downloading the update file to your docker host

  4. post successful download you can restart your container which will pick the latest update from the docker host

So to conclude you will have an endpoint outside Docker that download updates for you and handle the logic of starting/stopping the container with the correct update version.

Also not to mention it will be great to have a backup of previous updates which will help in case of a faulty update. You can use a rolling update file writer kind of mechanism for this.

This approach is great both in terms of Network and Security aspects.

Hope this helps. Thanks.

英文:

I do not think exposing an endpoint and uploading an entire file to the server is a great idea both due to Network and Security issues.

Currently, I do not have any idea about what those update files are, but by your approach container will be doing double work. (Doing its own job + downloading updates)

For copying the updated files you use a secure protocol like scp from local to the docker container. now assuming you have backups of update files in case of network failure while copying updates then this approach works.

Here is a little better strategy.

  1. Ideally all your update files should be hosted on docker host which is then mounted using volume to docker container

  2. Better way will be you should upload this update file to a cloud storage service that is highly scalable.

  3. Your storage trigger will hit an endpoint which will start downloading the update file to your docker host

  4. post successful download you can restart your container which will pick the latest update from the docker host

So to conclude you will have an endpoint outside Docker that download updates for you and handle the logic of starting/stopping the container with the correct update version.

Also not to mention it will be great to have a backup of previous updates which will help in case of a faulty update. You can use a rolling update file writer kind of mechanism for this.

This approach is great both in terms of Network and Security aspects.

Hope this helps. Thanks.

huangapple
  • 本文由 发表于 2023年4月4日 03:25:30
  • 转载请务必保留本文链接:https://go.coder-hub.com/75923103.html
匿名

发表评论

匿名网友

:?: :razz: :sad: :evil: :!: :smile: :oops: :grin: :eek: :shock: :???: :cool: :lol: :mad: :twisted: :roll: :wink: :idea: :arrow: :neutral: :cry: :mrgreen:

确定