Today I've been setting up my new rig and I've been hitting an issue, some programs will not launch. The three main programs I've been having issues with are:-Paint, won't start no matter what I do-Geforce Experience, starts the launcher but wont open the main program-League of Legends, Launcher works but trying to start the game usually wont work. Platform: Windows, Mac, Linux; Share: VK. Follow us on: About Launcher. The Feed The Beast Launcher is a launcher program, which presents users with a window to select accounts and settings, like the official Minecraft launcher. In addition, the user is also able to select modpacks, maps and texture packs to enhance the game experience. Organizers can also start a webinar (or attendees can join a webinar) to initiate the software download. Once the web browser launches, you will see the following: If the Launcher application is not installed (either first time joining or it was removed), then the GoTo Opener.dmg file will automatically start downloading.
Estimated reading time: 16 minutes
Welcome to Docker Desktop! The Docker Desktop for Mac user manual provides information on how to configure and manage your Docker Desktop settings.
For information about Docker Desktop download, system requirements, and installation instructions, see Install Docker Desktop.
Note
This page contains information about the Docker Desktop Stable release. For information about features available in Edge releases, see the Edge release notes.
Preferences
The Docker Preferences menu allows you to configure your Docker settings such as installation, updates, version channels, Docker Hub login,and more.
Choose the Docker menu > Preferences from themenu bar and configure the runtime options described below.
General
On the General tab, you can configure when to start and update Docker:
- Start Docker Desktop when you log in: Automatically starts Docker Desktop when you open your session.
- Automatically check for updates: By default, Docker Desktop automatically checks for updates and notifies you when an update is available. You can manually check for updates anytime by choosing Check for Updates from the main Docker menu.
- Include VM in Time Machine backups: Select this option to back up the Docker Desktop virtual machine. This option is disabled by default.
- Securely store Docker logins in macOS keychain: Docker Desktop stores your Docker login credentials in macOS keychain by default.
- Send usage statistics: Docker Desktop sends diagnostics, crash reports, and usage data. This information helps Docker improve and troubleshoot the application. Clear the check box to opt out.Click Switch to the Edge version to learn more about Docker Desktop Edge releases.
Resources
The Resources tab allows you to configure CPU, memory, disk, proxies, network, and other resources.
Advanced
On the Advanced tab, you can limit resources available to Docker.
Advanced settings are:
CPUs: By default, Docker Desktop is set to use half the number of processorsavailable on the host machine. To increase processing power, set this to ahigher number; to decrease, lower the number.
Memory: By default, Docker Desktop is set to use
2
GB runtime memory,allocated from the total available memory on your Mac. To increase the RAM, set this to a higher number. To decrease it, lower the number.Swap: Configure swap file size as needed. The default is 1 GB.
Disk image size: Specify the size of the disk image.
Disk image location: Specify the location of the Linux volume where containers and images are stored.
You can also move the disk image to a different location. If you attempt to move a disk image to a location that already has one, you get a prompt asking if you want to use the existing image or replace it.
File sharing
Use File sharing to allow local directories on the Mac to be shared with Linux containers.This is especially useful forediting source code in an IDE on the host while running and testing the code in a container.By default the
/Users
, /Volume
, /private
, /tmp
and /var/folders
directory are shared. If your project is outside this directory then it must be addedto the list. Otherwise you may get Mounts denied
or cannot start service
errors at runtime.File share settings are:
- Add a Directory: Click
+
and navigate to the directory you want to add. - Apply & Restart makes the directory available to containers using Docker’sbind mount (
-v
) feature.
Tips on shared folders, permissions, and volume mounts
- Shared folders are designed to allow application code to be edited on the host while being executed in containers. For non-code items such as cache directories or databases, the performance will be much better if they are stored in the Linux VM, using a data volume (named volume) or data container.
- By default, Mac file systems are case-insensitive while Linux is case-sensitive. On Linux, it is possible to create 2 separate files:
test
andTest
, while on Mac these filenames would actually refer to the same underlying file. This can lead to problems where an app works correctly on a Mac (where the file contents are shared) but fails when run in Linux in production (where the file contents are distinct). To avoid this, Docker Desktop insists that all shared files are accessed as their original case. Therefore, if a file is created calledtest
, it must be opened astest
. Attempts to openTest
will fail with the errorNo such file or directory
. Similarly, once a file calledtest
is created, attempts to create a second file calledTest
will fail. For more information, see Volume mounting requires file sharing for any project directories outside of/Users
.)
Proxies
Beast 2 App Launcher Does Not Work In Macbook
Docker Desktop detects HTTP/HTTPS Proxy Settings from macOS and automaticallypropagates these to Docker. For example, if you set yourproxy settings to
http://proxy.example.com
, Docker uses this proxy whenpulling containers.Your proxy settings, however, will not be propagated into the containers you start.If you wish to set the proxy settings for your containers, you need to defineenvironment variables for them, just like you would do on Linux, for example:
For more information on setting environment variables for running containers,see Set environment variables.
Network
You can configure Docker Desktop networking to work on a virtual private network (VPN). Specify a network address translation (NAT) prefix and subnet mask to enable Internet connectivity.
Docker Engine
The Docker Engine page allows you to configure the Docker daemon to determine how your containers run.
Type a JSON configuration file in the box to configure the daemon settings. For a full list of options, see the Docker Enginedockerd commandline reference.
Click Apply & Restart to save your settings and restart Docker Desktop.
Command Line
On the Command Line page, you can specify whether or not to enable experimental features.
Experimental features provide early access to future product functionality.These features are intended for testing and feedback only as they may changebetween releases without warning or can be removed entirely from a futurerelease. Experimental features must not be used in production environments.Docker does not offer support for experimental features.
To enable experimental features in the Docker CLI, edit the
config.json
file and set experimental
to enabled.To enable experimental features from the Docker Desktop menu, clickSettings (Preferences on macOS) > Command Line and then turn onthe Enable experimental features toggle. Click Apply & Restart.
For a list of current experimental features in the Docker CLI, see Docker CLI Experimental features.
On both Docker Desktop Edge and Stable releases, you can toggle the experimental features on and off. If you toggle the experimental features off, Docker Desktop uses the current generally available release of Docker Engine.
You can see whether you are running experimental mode at the command line. If
Experimental
is true
, then Docker is running in experimental mode, as shownhere. (If false
, Experimental mode is off.)Kubernetes
Docker Desktop includes a standalone Kubernetes server that runs on your Mac, sothat you can test deploying your Docker workloads on Kubernetes.
The Kubernetes client command,
kubectl
, is included and configured to connectto the local Kubernetes server. If you have kubectl
already installed andpointing to some other environment, such as minikube
or a GKE cluster, be sureto change context so that kubectl
is pointing to docker-desktop
:If you installed
kubectl
with Homebrew, or by some other method, andexperience conflicts, remove /usr/local/bin/kubectl
.- To enable Kubernetes support and install a standalone instance of Kubernetesrunning as a Docker container, select Enable Kubernetes. To set Kubernetes as thedefault orchestrator, select Deploy Docker Stacks to Kubernetes by default.Click Apply & Restart to save the settings. This instantiates images required to run the Kubernetes server as containers, and installs the
/usr/local/bin/kubectl
command on your Mac.When Kubernetes is enabled and running, an additional status bar item displaysat the bottom right of the Docker Desktop Settings dialog.The status of Kubernetes shows in the Docker menu and the context points todocker-desktop
. - By default, Kubernetes containers are hidden from commands like
dockerservice ls
, because managing them manually is not supported. To make themvisible, select Show system containers (advanced) and click Apply andRestart. Most users do not need this option. - To disable Kubernetes support at any time, clear the Enable Kubernetes check box. TheKubernetes containers are stopped and removed, and the
/usr/local/bin/kubectl
command is removed.For more about using the Kubernetes integration with Docker Desktop, seeDeploy on Kubernetes.
Reset
Reset and Restart options
On Docker Desktop Mac, the Restart Docker Desktop, Reset to factory defaults, and other reset options are available from the Troubleshoot menu.
For information about the reset options, see Logs and Troubleshooting.
Dashboard
The Docker Desktop Dashboard enables you to interact with containers and applications and manage the lifecycle of your applications directly from your machine. The Dashboard UI shows all running, stopped, and started containers with their state. It provides an intuitive interface to perform common actions to inspect and manage containers and existing Docker Compose applications. For more information, see Docker Desktop Dashboard.
Add TLS certificates
You can add trusted Certificate Authorities (CAs) (used to verify registryserver certificates) and client certificates (used to authenticate toregistries) to your Docker daemon.
Add custom CA certificates (server side)
All trusted CAs (root or intermediate) are supported. Docker Desktop creates acertificate bundle of all user-trusted CAs based on the Mac Keychain, andappends it to Moby trusted certificates. So if an enterprise SSL certificate istrusted by the user on the host, it is trusted by Docker Desktop.
To manually add a custom, self-signed certificate, start by adding thecertificate to the macOS keychain, which is picked up by Docker Desktop. Here isan example:
Or, if you prefer to add the certificate to your own local keychain only (ratherthan for all users), run this command instead:
See also, Directory structures forcertificates.
Note: You need to restart Docker Desktop after making any changes to thekeychain or to the
~/.docker/certs.d
directory in order for the changes totake effect.For a complete explanation of how to do this, see the blog post AddingSelf-signed Registry Certs to Docker & Docker Desktop forMac.
Add client certificates
Beast 2 App Launcher Does Not Work In Macbook Pro
You can put your client certificates in
~/.docker/certs.d/<MyRegistry>:<Port>/client.cert
and~/.docker/certs.d/<MyRegistry>:<Port>/client.key
.When the Docker Desktop application starts, it copies the
~/.docker/certs.d
folder on your Mac to the /etc/docker/certs.d
directory on Moby (the DockerDesktop xhyve
virtual machine).- You need to restart Docker Desktop after making any changes to the keychainor to the
~/.docker/certs.d
directory in order for the changes to takeeffect. - The registry cannot be listed as an insecure registry (see DockerEngine. Docker Desktop ignores certificates listedunder insecure registries, and does not send client certificates. Commandslike
docker run
that attempt to pull from the registry produce errormessages on the command line, as well as on the registry.
Directory structures for certificates
If you have this directory structure, you do not need to manually add the CAcertificate to your Mac OS system login:
The following further illustrates and explains a configuration with customcertificates:
You can also have this directory structure, as long as the CA certificate isalso in your keychain.
To learn more about how to install a CA root certificate for the registry andhow to set the client TLS certificate for verification, seeVerify repository client with certificatesin the Docker Engine topics.
Install shell completion
Docker Desktop comes with scripts to enable completion for the
docker
and docker-compose
commands. The completion scripts may befound inside Docker.app
, in the Contents/Resources/etc/
directory and can beinstalled both in Bash and Zsh.Bash
Bash has built-in support forcompletion To activate completion for Docker commands, these files need to becopied or symlinked to your
bash_completion.d/
directory. For example, if youinstalled bash via Homebrew:![Mac Mac](/uploads/1/3/3/9/133911619/747763155.png)
Add the following to your
~/.bash_profile
:OR
Zsh
In Zsh, the completionsystemtakes care of things. To activate completion for Docker commands,these files need to be copied or symlinked to your Zsh
site-functions/
directory. For example, if you installed Zsh via Homebrew:Fish-Shell
Fish-shell also supports tab completion completionsystem. To activate completion for Docker commands,these files need to be copied or symlinked to your Fish-shell
completions/
directory.Create the
completions
directory:Now add fish completions from docker.
Give feedback and get help
To get help from the community, review current user topics, join or start adiscussion, log on to our Docker Desktop for Macforum.
To report bugs or problems, log on to Docker Desktop for Mac issues onGitHub,where you can review community reported issues, and file new ones. SeeLogs and Troubleshooting for more details.
For information about providing feedback on the documentation or update it yourself, see Contribute to documentation.
Docker Hub
Select Sign in /Create Docker ID from the Docker Desktop menu to access your Docker Hub account. Once logged in, you can access your Docker Hub repositories and organizations directly from the Docker Desktop menu.
For more information, refer to the following Docker Hub topics:
Two-factor authentication
Docker Desktop enables you to sign into Docker Hub using two-factor authentication. Two-factor authentication provides an extra layer of security when accessing your Docker Hub account.
You must enable two-factor authentication in Docker Hub before signing into your Docker Hub account through Docker Desktop. For instructions, see Enable two-factor authentication for Docker Hub.
After you have enabled two-factor authentication:
- Go to the Docker Desktop menu and then select Sign in / Create Docker ID.
- Enter your Docker ID and password and click Sign in.
- After you have successfully signed in, Docker Desktop prompts you to enter the authentication code. Enter the six-digit code from your phone and then click Verify.
After you have successfully authenticated, you can access your organizations and repositories directly from the Docker Desktop menu.
Where to go next
- Try out the walkthrough at Get Started.
- Dig in deeper with Docker Labs examplewalkthroughs and source code.
- For a summary of Docker command line interface (CLI) commands, seeDocker CLI Reference Guide.
- Check out the blog post, What’s New in Docker 17.06 Community Edition(CE).
Downloading BEAST
BEAST can be downloaded from the following link:
This will download a disk image (a ‘.dmg’ file) probably into your Downloads folder.
The latest version of BEAST can always be found here: https://github.com/beast-dev/beast-mcmc/releases/latest
Installing JAVA
To run BEAST on Mac OS X, you will need to have Java installed. Older versions of Mac OS had Java installed by default but this is no longer the case. BEAST currently requires at least version 6 of Java and this can still be installed as an optional package from Apple. Alternatively, you can install the latest version of Java which is distributed free by Oracle. The former option is easier but the latest Java may give slightly better performance.
Installing Apple Java 6
You can download the ‘legacy’ Java 6 from here: https://support.apple.com/kb/dl1572.This will download an installer which will install Java and you are ready to go (you won’t need to restart the machine).
Installing Oracle Java 8
To get the latest version of Java you will need to download the Java JDK from http://www.oracle.com/technetwork/java/javase/downloads/index.html. Download and install the ‘JRE’ - this is the Java Runtime Environment. If you want to compile Java code you can install the JDK (Java Development Kit) instead. Once installed, you will automatically get updates to the latest version.
Warning: Do not install the Java software offered on the http://java.com website. This will install java only as a plug in to your web browser. This version of Java will not be able to run BEAST.
The Mac version of BEAST is not yet compatible with Java 10. Please use Java 8 or 9.
Installing BEAST
Double-clicking the disk image file will open the a virtual ‘disk’ in a Finder window. At this point the applications are still on the ‘disk’ created by the disk image. We suggest that you drag the entire folder into your
Applications
folder (either the main Applications folder or the one in your user folder). You can drag the folder by clicking, holding and then dragging the little white icon at the top of the disk image finder window.Mac OS X security
When running any of the applications in the BEAST package for the first time you may see a security dialog box. This is Mac OS X’s security protecting your system from unknown software:
Rather than double-clicking to run the application for the first time, you can control-click (or right-click) on the application icon and select
Open
. This will bring up a similar dialog box to the one about but this time it will have an Open
button which will override the security for this application only. You will only need to do this the first time you open an application but you will need to do it individually for each of the applications in the BEAST package.You can then drag the icons into your Dock if you want quick access to them.
BEAGLE acceleration library
We also strongly recommend that you install the BEAGLE library to accelerate BEAST’s computation (indeed some analyses are not possible without BEAGLE). For more information about BEAGLE and information about installing it, see here.
Installing a command-line version of BEAST
Mac OS X is particularly popular in computational biology because it is built upon a UNIX operating system which gives it access to a wide range of scientific software. BEAST can also be installed to run within the command-line environment provided by the Mac OS X Terminal.app. For instructions on installing BEAST for a UNIX command line see this page.
Homebrew package manager for Mac OS X
The above instructions will also work to install BEAST as a command-line tool in Mac OS X. However, the recommended way of installing BEAST for use in the Mac OS X Terminal is to use the Homebrew package manager.
If you use the Mac OS X command-line you are probably familiar with Homebrew. This is a simple and convenient way of installing and updating command-line software on the Mac. Homebrew provides a huge range of science and bioinformatics software and a list of packages can be found here. See the Homebrew website to get it installed.
To install BEAST using HomeBrew type:
To check BEAST is installed type:
If a new version of BEAST is released, to update you just need to type:
You can also install the latest development version but this is at your own risk: