![]() ![]() See it fails, by ls-ing the tmpand see xyz is a regular dir.Then do a symlink making xyz to point to abc: ln -s abc xyz.Inside it, create an abc dir and throw some contents there.įirst let's try the "normal" way and see it fail.In a git-bash go to /c and create a temporary dir tmp.Check in windows host: Well check both abc and xyz from ouside the container.Check in ubuntu container: We'll see the changes also in abc from within the docker.Run docker: We'll then run docker with ubuntu and change contents in xyz.Create symlink: We'll create the symlink in windows and see it.See it fail: We'll try to make a symlink and see it fail.Preparation: Prepare a temporary dir with some files within the abc directory.Issue export MSYS=winsymlinks:nativestrict in git-bash.How could I make a windows host to see the "demapped contents of symlinks" to make the IDE see the vendored content that is linked from inside docker linux containers? It seems the original service still listens not to 127.0.0.1:445 but to 0.0.0.0:445 so still "blocking" the attachment to listen to 192.168.4.83:445.It seems the IP is only for internal docker networking but not seen from the host.Mapping an IPīut is seems that this still creates problems: If I map to another port, like 10445:445 then the client is unable to access it, as client samba ports in windows seem to be not configurable. If I turn down the local SMB, then in the next reboot, docker is unable to share C:\ into docker (I was not consciuos it does this sharing via SMB, could it be turned into a NFS or so?) c/Users/xavi/Documents/repos/test_samba:/mountĬommand: samba.sh -s "test_samba /mnt/repos/test_samba yes no yes all"īut this conflicts as 445 is locally already used. ![]() To do so, I setup this docker-compose: version: "3.7" Initially I thought that as well as in the old topology a linux server just shared the filesystem via samba and the windows could just read the symlinks contents as they were demapped at the serverside and not the clientside, I thought that I could run another docker machine with a samba server just to locally share the "things seen from the linux" into the Windows host again. This forces us to look for an alternate solution. I already know Windows does not support symlink compatible with linux symlinks. This makes the IDE to be unable to follow C:\repos\app-1\vendor\lib-x and all the code-completion helpers are broken. The problem is now the IDE: While it reads the files in C:\repos\app-1, the symlink that has been created within the linux containers can't be seen from the host. This does work perfectly and also the repositories work fine if we run the applications in the local dockers Problem with symlinks in linux container and windows host We made the symlinks within the app-1 and app-2 to lib-x and lib-y from inside the linux containers. We now have some devel machines FROM ubuntu:xxx and run them mounting the volumes. We just installed docker desktop in Windows and shared C:\repos from the host into the dockers. We now decided that we are not going to use anymore the office-servers and we are going to setup all the development within docker containers. The developers need the connection to the server to develop and we wanted to mutate to local dockers so we can make the devels work from home. This has been working like this for nearly a decade and works perfectly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |