![]() ![]() ![]() I use these plugins to help me be more productive on the command line, they provide command aliases, highlighting and enhanced command completions. The less sections are loaded the faster the shell will load, so I enable the sections that are of use to me. The SPACESHIP_PROMPT_ORDER array enables you to define which sections are enabled or disabled in the prompt, this is optional but can improve the performance of the prompt. Git # Git section (git_branch + git_status)īattery # Battery level and status jobs # Background jobs indicator SPACESHIP_PROMPT_ORDER =( dir # Current directory section I’ve configured JetBrains Mono as my default font to be used across all shells. Windows Terminal is a great open source terminal emulator from Microsoft enabling you to switch between different shells with ease and is fully customisable. I downloaded the font from the JetBrains website and installed it in Windows. It has support for ligatures, which hugely helps with readability of code, reducing noise by merging symbols and balancing whitespace between characters more efficiently than regular fonts. I like a good font that is easy to read, my current preference at the moment is JetBrains Mono, which is a free and open source typeface designed for developers, in fact it is the very font that you are reading right now. I’m currently running Ubuntu 20.04 LTS which I installed from Microsoft Store after installing WSL on Windows 10. WSL comes into its own for SharePoint Framework (SFPx) development, which uses an open source technology stack, where developing in WSL2 Linux containers hugely improves the performance of installing and building solutions over using the Windows filesystem. Well yes, but what the really nice thing about WSL2 is, how the WSL2 Linux containers can be interacted with from the Window OS, allowing you to do things like, launching Visual Studio code installed in Windows from within the Linux container or opening the Linux file system in File Explorer in Windows, making for seamless switching and really blurring the lines between the two operating systems. Windows Subsystem for Linux (WSL) 2 gives developers the ability to run Linux containers, benefiting from the improved filesystem performance, from within Windows.īut wait, doesn’t Docker already do that? This post documents my setup for open source and SharePoint Framework development, why I use certain components and the configuration steps I took. As a Mac user, I have benefitted from years of developer workflow improvements and enhancements at the command line but now I can bring those into Windows. Windows Subsystem for Linux (WSL) 2 has really changed the game when it comes to open source development on Windows. Log out and back in to confirm the changes.My WSL2 and Windows Terminal setup 20 December 2020 To solve this issue, add the current user to the Docker group via usermod command: sudo usermod -aG docker Ģ. You need to be able to access the Docker engine without using the sudo command.ġ. Not having the proper user privileges also triggers the error. Sudo chown :docker /your/file/location Method 4: Add Your User to the Docker Group Finally, you can change the file ownership with:.dockerignore file to your current build, thus excluding the files your build can’t access. You can simply remove the files in question by deleting them, but this affects any other builds using the same files.There are several ways to resolve the issue of ownership of used files: If there is a problem with the file ownership, the error report will list out the files that the docker build command cannot access.ģ. Check the output for each container, keeping an eye out for an “ cannot connect to the Docker daemon” error report. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |