Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using volume mounts vs bind mounts for the IoT Edge system modules #7408

Open
anttikes opened this issue Dec 18, 2024 · 1 comment
Open

Using volume mounts vs bind mounts for the IoT Edge system modules #7408

anttikes opened this issue Dec 18, 2024 · 1 comment
Assignees

Comments

@anttikes
Copy link

The documentation instructs using bind mounts for persistently storing the data of edgeAgent or edgeHub modules on the host filesystem.

Docker's own documentation recommends using volume mounts instead.

Is there any clear reason why bind mounts are preferred in the documentation? Would the same benefits (i.e. robustness) be achieved by using volume mounts?

In what kind of a situation would it be necessary to manually manipulate the files persisted by the system modules from the host side?

@vipeller vipeller self-assigned this Dec 19, 2024
@mikanygTC
Copy link

We have chosen to ignore the documentation and opted in for using volume mounts as per the recommended docker approach.

I have been following Azure IoT Edge since 1.0, and I think the docs where written a long time ago, and might haven't been updated to reflect dockers recommend approach.

bind mounts mostly makes sense if you need to be in control of the folder on the host, either by sharing with other containers or daemon on the host. Otherwise I would go with volumen mounts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants