Skip to content

Conversation

@stevvooe
Copy link
Contributor

@stevvooe stevvooe commented Dec 6, 2024

Description

After some discussion with the team, we've added a few more conditions.

Related issues or tickets

Reviews

  • Technical review
  • Editorial review
  • Product review

@netlify
Copy link

netlify bot commented Dec 6, 2024

Deploy Preview for docsdocker ready!

Name Link
🔨 Latest commit b73e178
🔍 Latest deploy log https://app.netlify.com/sites/docsdocker/deploys/675a182489bf690008abcc60
😎 Deploy Preview https://deploy-preview-21582--docsdocker.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link

@rodnymolina rodnymolina left a comment

Choose a reason for hiding this comment

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

LGTM

- 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.

Choose a reason for hiding this comment

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

s / starting / creating

Co-authored-by: Nick Sieger <nicksieger@gmail.com>
- 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 creating a file-sync.
- 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

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

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.

Co-authored-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
@dvdksn dvdksn merged commit e0fb9b3 into docker:main Dec 12, 2024
14 checks passed
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

Successfully merging this pull request may close these issues.

4 participants