https://medium.freecodecamp.org/jazz-up-your-zsh-terminal-in-seven-steps-a-visual-guide-e81a8fd59a38
- Install iTerm2, OhMyZsh, Custom fonts, Themes & plugins
- Enable shell integrations
https://medium.freecodecamp.org/jazz-up-your-zsh-terminal-in-seven-steps-a-visual-guide-e81a8fd59a38
Sometimes the default docker-machine (default.vbox under .docker\machine\machines\default folder) could error out with an error like "machine does not exist".
A simpler way to resolve this situation is to look for "default.vbox.*" files in the same folder.
You'd most probably find files like - default.vbox.new or default.vbox-prev or default.vbox-tmp
if there's a "default.vbox.tmp" make a copy of it and rename it to "default.vbox"!
That's it.
You've restored the default vm successfully!
Have fun.
java -jar plantuml.jar -metadata image.pngExtract the source plantuml text from the plantuml diagram. This is a super cool feature as you just need to save the diagram & not worry about archiving the sources!
Follow instructions from http://plantuml.com/pdf to generate PDF output from plantuml.
java -jar plantuml.jar -tpdf <filename>
in short, a bunch of dependent jar files need to be copied to the same path as of plantuml.jar the dependencies can be downloaded from here
Change the guest OS type to Ubuntu 64 bit from 32 bit How to troubleshoot booting to a black screen on virtualbox https://askubuntu.com/a/692746/486048
Eject & Re-load the guest additions iso Unable to mount the CD/DVD image on the machine Sandbox https://askubuntu.com/a/672493/486048
VBoxManage.exe: error: Raw-mode is unavailable courtesy of Hyper-V. (VERR_SUPDRV_NO_RAW_MODE_HYPER_V_ROOT)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole
Windows hypervisor config. might be breaking other hypervisors (!@#!?!)
To fix this, disable hypervisor during boot time - using bcdedit as in this link.
VBoxManage.exe: error: VT-x is not available (VERR_VMX_NO_VMX)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole
It so happens when you add an existing VM, you'd get this error - thanks to virtualization capability settings in different machines. Other possbile reasons are discussed here in depth - https://forums.virtualbox.org/viewtopic.php?f=6&t=58820