-
Notifications
You must be signed in to change notification settings - Fork 124
docker can't access to volume with screen #4822
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
Comments
You can get slightly further if you run
I haven't figured out how to run screen without the tty to fix the buggy permissions there. This bug also affects version 2.3.5.0 (edge channel). I uploaded a diagnostic log as well: |
@dpkirchner I did the command above
But not sure how to proceed. Docker |
I'm not sure, you got a lot further along than I did. FWIW, I run in to exactly the same bug in 2.3.0.4 as I did in 2.3.5.0. There's a StackOverflow comment about the issue suggesting a solution that may work for some cases: https://stackoverflow.com/a/60582083 It doesn't work for my specific use case, unfortunately, but it might help you out. |
I met this issue on 2.3.0.4(46911) too. And the log is: |
Until this is fixed, here are two workaround methods that worked for me: https://stackoverflow.com/a/63595817/1456285 |
I have tried using method 1 from above link -> https://stackoverflow.com/a/63595817/1456285 I did enter into terminal but after that how to navigate? |
Once you have terminal access to the VM, you can find the volume data in the usual place, i.e. docker run -it --privileged --pid=host debian nsenter -t 1 -m -u -n -i sh / # ls -lah /var/lib/docker/volumes/
total 72
drwx------ 10 root root 4.0K Aug 27 11:34 .
drwx--x--x 15 root root 4.0K Oct 9 16:07 ..
drwxr-xr-x 3 root root 4.0K Aug 26 10:44 14ce94e174839f1947efa6fcbf5ac1fb2ea3b0f0b3f25311fee333ee374576b6
drwxr-xr-x 3 root root 4.0K Aug 25 12:34 34eb2bd80931ff954e1da80c5383beb4def61129d4005432b77080531cd10a5a
drwxr-xr-x 3 root root 4.0K Aug 27 11:34 830de2ce31519c921b50c448964b54517ca4461d337b56a9fd6e5b354ace3247
drwxr-xr-x 3 root root 4.0K Aug 25 12:34 data-layer_mongo_data
drwxr-xr-x 3 root root 4.0K Aug 26 11:01 ebb440184703bfad17184bd5ff74b677b50d74b8f0fbdd116506a1fcacfb00cd
drwxr-xr-x 3 root root 4.0K Aug 27 11:27 hawakening-services_back-end_log
drwxr-xr-x 3 root root 4.0K Aug 27 11:27 hawakening-services_front-end_log
drwxr-xr-x 3 root root 4.0K Aug 27 11:27 hawakening-services_mongo_data
-rw------- 1 root root 64.0K Oct 9 16:07 metadata.db / # ls -lah /var/lib/docker/volumes/data-layer_mongo_data/_data/
total 1352
drwxr-xr-x 4 999 ping 4.0K Aug 27 11:35 .
drwxr-xr-x 3 root root 4.0K Aug 25 12:34 ..
-rw------- 1 999 ping 46 Aug 25 12:34 WiredTiger
-rw------- 1 999 ping 21 Aug 25 12:34 WiredTiger.lock
-rw------- 1 999 ping 1.2K Aug 27 11:35 WiredTiger.turtle
-rw------- 1 999 ping 84.0K Aug 27 11:35 WiredTiger.wt
-rw------- 1 999 ping 4.0K Aug 27 11:35 WiredTigerLAS.wt
-rw------- 1 999 ping 20.0K Aug 27 11:35 _mdb_catalog.wt
-rw------- 1 999 ping 20.0K Aug 27 11:35 collection-0--6268495467305357123.wt
-rw------- 1 999 ping 388.0K Aug 25 12:34 collection-10--6268495467305357123.wt
-rw------- 1 999 ping 132.0K Aug 26 10:14 collection-12--6268495467305357123.wt
-rw------- 1 999 ping 264.0K Aug 26 10:14 collection-14--6268495467305357123.wt
-rw------- 1 999 ping 36.0K Aug 27 11:35 collection-2--6268495467305357123.wt
-rw------- 1 999 ping 24.0K Aug 26 10:14 collection-4--6268495467305357123.wt
-rw------- 1 999 ping 28.0K Aug 25 12:34 collection-8--6268495467305357123.wt
drwx------ 2 999 ping 4.0K Aug 27 11:35 diagnostic.data
-rw------- 1 999 ping 20.0K Aug 27 11:35 index-1--6268495467305357123.wt
-rw------- 1 999 ping 40.0K Aug 25 12:34 index-11--6268495467305357123.wt
-rw------- 1 999 ping 60.0K Aug 26 10:14 index-13--6268495467305357123.wt
-rw------- 1 999 ping 64.0K Aug 25 13:47 index-15--6268495467305357123.wt
-rw------- 1 999 ping 36.0K Aug 27 11:35 index-3--6268495467305357123.wt
-rw------- 1 999 ping 24.0K Aug 26 10:14 index-5--6268495467305357123.wt
-rw------- 1 999 ping 12.0K Aug 27 11:35 index-6--6268495467305357123.wt
-rw------- 1 999 ping 24.0K Aug 25 12:34 index-9--6268495467305357123.wt
drwx------ 2 999 ping 4.0K Aug 26 10:15 journal
-rw------- 1 999 ping 0 Aug 27 11:35 mongod.lock
-rw------- 1 999 ping 36.0K Aug 27 11:35 sizeStorer.wt
-rw------- 1 999 ping 114 Aug 25 12:34 storage.bson / # exit |
Hello here is the way am running my docker : I don't get why tty is not found. Can someone help me ? |
I also don't have tty file.
|
I don't have the tty file too. I'm using latest docker desktop 2.5.0.1 for mac. |
I don't have the tty file too. |
Me too |
I still met this issue now and my docker desktop version is: 2.5.0.1 (49550) and Channel: stable. |
met this issue too:
Server: Docker Engine - Community |
Looks like they changed it to a button "CLI" in the UI see my post / img here https://stackoverflow.com/a/65203563/1484447 |
Hello, did you find a solution ? |
A workaround works for me: https://rocky-chen.medium.com/docker-unable-to-access-to-volume-with-screen-for-mac-9d016f5420e6 |
I don't have tty either: Client: Docker Engine - Community Server: Docker Engine - Community But there's a few good news here for you based on #4822 (comment) and in VsCode! |
If you can't find your tty, it maybe because you can no longer screen into the Docker Vm on macOS. The following solution worked for me: I used "method 1":
I'm on Docker 20.10.2 and macOS: 10.17.7 |
I can confirm the same bug and work-around here on my Docker for MacOS
Relevant versions:
|
same issue
i have same issue |
Me too! no tty file. |
Ran into the same issue, when I'm trying to fix another issue #1396 |
With no tty file. |
Is there a solution? |
😪 |
there is still no fix |
🥲 Some workarounds: https://stackoverflow.com/a/36330903 https://stackoverflow.com/a/55648186 |
Having the same problem. add this in .zshrc |
Additional: This doesn't create the container over and over again. |
Issues go stale after 90 days of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
In order to prevent |
have same problem can't run screen for my program, on volume.. p.s. sorry problem for linux (not for clear mac) |
/remove-lifecycle stale |
Closed issues are locked after 30 days of inactivity. If you have found a problem that seems similar to this, please open a new issue. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
Expected behavior
Allows to acces by terminal to tty related to docker
Actual behavior
Information
Diagnostic logs
Steps to reproduce the behavior
The text was updated successfully, but these errors were encountered: