Skip to content

harmonia: one more pass for bind volumes #21582

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.

Sign up for GitHub

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

Merged
merged 4 commits into from
Dec 12, 2024
Merged

harmonia: one more pass for bind volumes #21582

Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
ec6619d
harmonia: one more pass for bind volumes
stevvooe Dec 6, 2024
bdb5281
Update content/manuals/harmonia/_index.md
stevvooe Dec 7, 2024
cd190b2
Update content/manuals/harmonia/_index.md
stevvooe Dec 7, 2024
b73e178
Update content/manuals/harmonia/_index.md
stevvooe Dec 11, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion content/manuals/harmonia/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -263,7 +263,9 @@ Run `docker harmonia doctor` to print helpful troubleshooting information.
- KinD does not run on Project Harmonia due to some hard-coded assumptions to ensure it's running in a privileged container. K3d is a good alternative.
- Containers cannot access host through DNS `host.docker.internal`.
- File binds (non-directory binds) are currently static, meaning changes will not be reflected until the container is restarted. This also affects Compose configs and secrets directives.
- Bind mounts, such as `-v /localpath:/incontainer` in the `docker run` command, are not supported without using a file-sync.
- Bind _mounts_, such as `-v /localpath:/incontainer` in the `docker run` command, require starting a file-sync.
Copy link

@rodnymolina rodnymolina Dec 6, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s / starting / creating

- Starting a file-sync for a directory with a large amount of may take extra time to sync and become ready for use in a container.
- Bind _volumes_, such as those created with `docker volume create --driver local --opt type=none --opt o=bind --opt device=/some/host/path myvolname` or via the compose equivalent, are not supported.
Copy link
Contributor

@dvdksn dvdksn Dec 9, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: local is the default driver, so can be omitted in this example for brevity.

Suggested change
- Bind _volumes_, such as those created with `docker volume create --driver local --opt type=none --opt o=bind --opt device=/some/host/path myvolname` or via the compose equivalent, are not supported.
- Bind _volumes_, such as those created with `docker volume create --opt type=none --opt o=bind --opt device=/some/host/path myvolname` or via the compose equivalent, are not supported.

Copy link
Contributor Author

@stevvooe stevvooe Dec 11, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I actually left this in so the context would be clear. Feel free to commit suggestion if you think its not necessary.

- Port-forwarding for UDP is not supported.
- Docker Compose projects relying on `watch` in `sync` mode are not working with the `tar` synchronizer. Configure it to use `docker cp` instead, disable tar sync by setting `COMPOSE_EXPERIMENTAL_WATCH_TAR=0` in your environment.
- Some Docker Engine features that let you access the underlying host, such as `--pid=host`, `--network=host`, and `--ipc=host`, are currently disabled.
Loading