I am able to run the hello-world-nginx Docker container running Kitematic on Windows 7. The following tutorial shows that the website_files is accessible from the Mac Finder:
https://kitematic.com/docs/nginx-web-server/
On Windows, I do not see the Edit Files section in Kitematic and the Volumes tab is empty.
I am new to Docker, Kitematic and VirtualBox.
Are volumes supported yet in Kitematic 0.7.6 for Windows? I was not prompted to mount a volume and I don't see any way to do it in Kitematic.
I just installed today on windows 10 and yes it supports volumes, but actually thats based on the image configuration. I see you have posted this long time ago, give it another go ur update what do u have and you should find it there.
Guess only in the OSX version you can always alter them... for the latest mongo it works on Win too, but it also has the mounts directly in the dockerfile:
https://github.com/docker-library/mongo/blob/191cc63288fb44c2fd147eac27ade07ae4b6b0b5/3.2/Dockerfile#L58
Guess it can be easily added too any dockerfile in a similar way then.
Related
I'm on windows 10 and I'm encountering Docker on Windows crashing on startup.
I just installed docker on windows and have a couple of containers spinning up (last night). I've been able to use it but after reboot, or shutdown, this was the behaviour ever since. Pretty unstable.
It looks like this and terminates after a while without any prompt of an error.
More info that I have Hyper-V installed on my machine and "Use the WSL 2 based engine" option enabled on docker.
On my end, I was able to solve this by:
Going to Apps & Features
Search for Ubuntu (or any linux distro you've installed)
Click on it and navigate to Advance options
Click on Reset button.
Also, try to trial and error which docker on windows version is stable with your system.
Hope that helps.
I am trying to connect docker running on MacOS. I have a Windows 10 VM running on Mac and instead of installing docker again in VM(which usually runs in many issues), I'd like to connect to docker running on Mac. Can someone point me to a tutorial or some answer. I am novice in docker.
Have you already installed Docker Desktop for Mac?
After you've got Docker up and running, tell it where your projects are:
Open Docker Preferences
Click the File Sharing icon in the icon bar at the top of the window
Click the plus button at the bottom of the path list
Select the folder that contains all your projects
Click Apply & Restart
If you need to have your Windows VM connect to your Docker containers running on macOS, you'll need find out if Windows can access your Mac via networking. You will also need to modify your Windows hosts file to point to your Mac's IP address.
I have installed debian 9.3 on HP DL20 Gen9. When Debian 9.3 start, what happen is that the screen of the system appear like on the picture after the grub goes. any help?
Try booting your computer up in safe mode from Grub. Install updates and restart.
If it happens again you probably need to configure your graphics card for your installation.
Re-install Debian 9, when in the Software selection menu,
don't enable Debian Desktop Environment. If you need a desktop environment, simply enable certain Desktop environments.
In this case, I'm using Cinnamon. Until now there are no problems.
Thanks.
I find a solution. I used "nomodeset on the boot", and the screen appear normaly. I have used another tty2 and i get connected with the shell.
nano /etc/default/grub
i find this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
and i have changed it to this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet nomodeset"
I recently got a new MacBook Pro running OS X 10.10.2, and I installed Boot2Docker 1.5.0 on it. Aside from Chrome, this is the first program I installed on my new machine. However, when I try to run it, the terminal window opens up for a few seconds, saying boot2docker is up, and then my computer restarts automatically.
I tried to uninstall 1.5.0 and install 1.4.1 (as that is what I was using on my last machine), but I encountered the same problem.
The last thing I see before my laptop restarts is the second image, and the error report my computer shows after the restart is the first image here:
http://i.imgur.com/6TD0Jt6.png
Has anyone every had this problem before, or know how I can address it? Thanks!
Instead of using Boot2Docker, have you considered making a linux virtual machine on your mac? Then you would just run docker on the virtual machine.
This fixed all of the problems I had with boot2docker.
The point of boot2docker is to enable docker to run on your mac. If you use a linux VM you will no longer need boot2docker.
I posted this question in AskDifferent as well, and it turns out there was a problem with OS X Security Update 2015-003 and boot2docker/virtualbox, as per this link: https://github.com/boot2docker/boot2docker/issues/800
Updating my version of VirtualBox remedied the situation.
I installed RHEL 6.4 server under Parallels 7 on my Mac OS 10.8 just now from an iso file I just downloaded from RedHat. The installation seemed to proceed ok, but at the end I'm left with a screen with a gray bar followed by the text "RedHat Enterprise Linux Server 6.4" with no obvious way how to login.
If I shut down the machine I see it running the shutdown scripts. If I boot it I see the boot scripts and they all look ok. But I always end up at that same screen with no way to login.
I can enter characters in the screen, but there is no Linux prompt at all.
Anybody know what to do next? I couldn't glean anything fro the RedHat install manual.
Thanks,
doug
I had the same problem. The issue is the X-win server will not start because Parallels tools breaks the framebuffer with the RHEL 6.4 update. This is especially easy to see because a fresh install works fine until you install Parallels tools.
When you see the "select system to boot" message, hit the key that allows you to edit the boot arguments. Add a "3" to the end to force the startup to runlevel 3 (which is a console login without the GUI).
After logging in, type the command "starts" and you will see that it fails. Once you are able to fix this problem, the normal bootup into the GUI login will also work.
I had to downgrade the video driver subsystem back to 6.3 for it to start working, and you also have to add an exclusion to yum to prevent it from updating and removing the fix. This will be necessary until Parallels releases an updated tools that addresses this issue. There is a procedure I found in the CentOS forums for how to do this, sorry I don't have the link.