Repository For Mac Os X

Posted : admin On 1/30/2022

Estimated reading time: 16 minutes

This project (the boot2docker OS X Installer) is officially deprecated in favor of the new Docker Toolbox. After you have successfully installed Git on Mac, you’ll need to provide secure communication with your Git repositories by creating and installing SSH keys. Creating SSH keys on Mac To communicate with the remote Git repository in your Beanstalk account from your Mac, you will need to generate an SSH key pair for that computer.

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.

Macintosh

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 and Test, 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 called test, it must be opened as test. Attempts to open Test will fail with the error No such file or directory. Similarly, once a file called test is created, attempts to create a second file called Test will fail. For more information, see Volume mounting requires file sharing for any project directories outside of /Users.)

Proxies

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.

Repository For Mac Os X64

To enable experimental features in the Docker CLI, edit the config.jsonfile 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. IfExperimental 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

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.dfolder 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:

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:

  1. Go to the Docker Desktop menu and then select Sign in / Create Docker ID.

  2. Enter your Docker ID and password and click Sign in.

  3. 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).

mac, tutorial, run, docker, local, machine

Current Stable Version

The current stable release of GIMP is 2.10.22 (2020-10-04).

We think your OS is Well, we don't actually know. Either JavaScript is disabled, or I am not working quite right... So I am showing you all the options.

Show downloads for GNU/LinuxOS XMicrosoft WindowsAll

GIMP for Unix-like systems

If available, the official package from your Unix-like distribution is the recommended method of installing GIMP!

The flatpak build is new and has known limitations, though it will likely provide faster updates, following GIMP releases closely.
Therefore choose your installation medium according to your needs.

Flatpak build available in: i386, x86-64, ARM and AArch64.

Flatpak additional instructions

The flatpak link above should open your software installer and prompt you to install GIMP. Yet it may not work out-of-the-box on some platforms since the flatpak technology is new. If that is the case, ensure flatpak is installed and if clicking the link still does not prompt to install GIMP, then manually install by command line:

flatpak install https://flathub.org/repo/appstream/org.gimp.GIMP.flatpakref

Safe

Once installed, it will be made available exactly the same way as other applications (menus, desktop overview, or any specific application launch process used by your desktop).
If this is not the case, we suggest to report a bug to your desktop or distribution asking for proper support of flatpak. In the meantime, you can still run it by command line (not as the recommended method, only a workaround):

flatpak run org.gimp.GIMP//stable

This installation will also provide regular update. You don't have to come back on this page and install again (it will not work!) when a new version of GIMP is released. Instead if your distribution and/or desktop has a good support for flatpak, it should propose to perform updates.
Once again, if your distribution does not have proper support, you can always fall back to using the following command line:

flatpak update

Systems without flatpak support

GIMP can also run on Solaris and is available for the BSD family of systems such as FreeBSD and OpenBSD.

Please refer to the documentation for your Unix-like system on the installation of software.

GIMP for macOS

Note: the currently available package provides GIMP 2.10.14 and has not yet updated to the latest version, GIMP 2.10.22. We're working on that, please check back later.

The download links above will attempt to download GIMP from one of our trusted mirror servers. If the mirrors do not work or you would rather download directly from our server, you can get the direct download here.

Supported OS: macOS 10.9 Mavericks or over

Since the 2.8.2 version, GIMP runs on OSX natively. No X11 environment is required.

Native build

Is macintosh repository safe

The official GIMP 2.10 DMG installer (linked above) is a stock GIMP build without any add-ons. Just open the downloaded DMG and drag and drop GIMP into your 'Applications' folder.

The SHA256 hash sum for gimp-2.10.14-x86_64-1.dmg is: 52654d85f894834f6c134c724beff3eddf212a1bda317299314322cfeff97e52

Check it on VirusTotal: gimp-2.10.14-x86_64-1.dmg

Repository For Mac Os X

Older Downloads

Previous installers for OSX can be found here: download.gimp.org.

Macports

An easy way to compile and install GIMP and other great Free software on your Mac is by using Macports. The installer allows you to choose from a large directory of packages. To install gimp using Macports, you simply do sudo port install gimp once you have Macports installed.

Last we checked, the GIMP port file pointed to the current stable release and we have reports from people who've built GIMP successfully this way.

Homebrew

Homebrew is similar to Macports and provides packages (aka formulas) to install, either by compiling them from source or by using pre-made binaries. There are indications that there is now a formula for GIMP, installable with: brew tap homebrew/cask && brew cask install gimp.

NOTE! Please be aware that it was announced recently that Homebrew is using analytics. To turn this off in homebrew then run: brew analytics off
You can read more about this on Brew Analytics.

Fink

Fink is a package repository that offer mostly precompiled binaries. It provides the apt-get command known to e.g. Debian and Ubuntu users, and installing GIMP is as easy as sudo apt-get install gimp once you have installed the Fink installer.
If there's no binary package, then fink install gimp will compile GIMP from source.

Disclaimer: we haven't been able to determine if it is possible to install or build recent GIMP from Fink. Last we checked, GIMP 2.6.12 appears to be the most recent GIMP package that is offered there.

GIMP for Windows

The download links above will attempt to download GIMP from one of our trusted mirror servers. If the mirrors do not work or you would rather download directly from our server, you can get the direct download here.

Supported OS: Windows 7 or over

These links download the official GIMP installer for Windows (~200 MB). The installer contains both 32-bit and 64-bit versions of GIMP, and will automatically use the appropriate one.

BitTorrent is a peer-to-peer file sharing system. It works by downloading GIMP from a distributed network of BitTorrent users, and may improve download speed dramatically. Choosing this option will download the torrent file for the GIMP installer. You may need to install a torrent client to make use of this file. Learn more...

Hash Sum

The SHA256 hash sum for gimp-2.10.22-setup.exe is: f7851c348584ce432dfd8e69b74a168c7dec33ebfddc29c96ad2d6b83aded083

Check it on VirusTotal: gimp-2.10.22-setup.exe

Older Downloads

  • Previous v2.10 installers for Windows can be found here: download.gimp.org.
  • Previous v2.8 installers for Windows can be found here: download.gimp.org.

GIMP User Manual

These links download language-specific Windows installers for GIMP's local help. By default, they will place the help files with your GIMP installation.

Note: GIMP uses online help by default. If you want to use this local help offline, you will need to change GIMP's help settings.

  1. In GIMP, select [Edit] > [Preferences] > [Help System]
  2. For 'User manual', select 'Use a locally installed copy'
  3. Under 'Help Browser', you can choose between your system's web browser and GIMP's help browser plugin (if available).

See the online help for more settings.

  • Chinese Simplified (39 MB)
  • Catalan (40 MB)
  • Danish (39 MB)
  • Dutch (39 MB)
  • English (39 MB)
  • English (United Kingdom) (39 MB)
  • Finnish (39 MB)
  • French (41 MB)
  • German (41 MB)
  • Greek (38 MB)
  • Italian (43 MB)
  • Japanese (39 MB)
  • Korean (40 MB)
  • Norwegian Nynorsk (35 MB)
  • Portuguese Brazilian (40 MB)
  • Romanian (39 MB)
  • Russian (40 MB)
  • Spanish (40 MB)

Mac Os 9 Games

Source for version 2.10 (Stable)

Repository mac os x

GIMP releases available from gimp.org and its mirrors contain the source code and have to be compiled in order to be installed on your system.

For instructions, how to build GIMP from source code, please see this page.

GIMP 2.10.22 is now available at https://download.gimp.org/mirror/pub/gimp/v2.10/. You may want to read the Release Notes for GIMP 2.10.

To allow you to check the integrity of the tarballs, here are the hashes of the latest releases:

gimp-2.10.22.tar.bz2 (sha256):
2db84b57f3778d80b3466d7c21a21d22e315c7b062de2883cbaaeda9a0f618bb
gimp-2.10.20.tar.bz2 (sha256):
e12f9f874b1a007c4277b60aa81e0b67330be7e6153e5749ead839b902fc7b3c
gimp-2.10.18.tar.bz2 (sha256):
65bfe111e8eebffd3dde3016ccb507f9948d2663d9497cb438d9bb609e11d716
gimp-2.10.16.tar.bz2 (sha256):
cbf9fe9534b913a9487b00cd9710cbc569bfd71fdd2f8c321547701a7d70cbeb
gimp-2.10.14.tar.bz2 (sha256):
df9b0f11c2078eea1de3ebc66529a5d3854c5e28636cd25a8dd077bd9d6ddc54
gimp-2.10.12.tar.bz2 (sha256):
7d80b58e0784120d57d327294f6a1fda281ff51a61935c2cd764da281acaac71
gimp-2.10.10.tar.bz2 (sha256):
12d1f243265c7aee1f2c6e97883a5c90ddc0b19b4346cf822e24adbb6c998c77
gimp-2.10.8.tar.bz2 (sha256):
d849c1cf35244938ae82e521b92b720ab48b8e9ed092d5de92c2464ef5244b9b
gimp-2.10.6.tar.bz2 (sha256):
4ec8071f828e918384cf7bc7d1219210467c84655123f802bc55a8bf2415101f
gimp-2.10.4.tar.bz2 (sha256):
ffb0768de14a2631b3d7ed71f283731441a1b48461766c23f0574dce0706f192
gimp-2.10.2.tar.bz2 (sha256):
1cb0baaecdefe44d371a15f2739a1bcbce4682336b4ccf8eb7b587ce52c333eb
gimp-2.10.0.tar.bz2 (sha256):
7fcc96fb88cb0a0595d2610f63a15dec245bb37bf9db527d37a24fb75e547de2

Repository For Mac Os X 10.10

GIMP help files are available at https://download.gimp.org/mirror/pub/gimp/help/.

Please consider using one of the mirrors listed below.

Development snapshots

We now have a separate page for development versions of GIMP.

Repository For Mac Os X 10.8

Want to check out the GIMP development release?
Get it on our development downloads page.

FTP and Web Mirrors

Repository For Mac Os X 10.13

We had a server move a while back that caused us to lose our existing mirrors (moved from physical to virtual server and to an environment that doesn't allow FTP access). On the plus side, we are now able to offer rsync access to download.gimp.org.

If you are running one of the existing GIMP mirrors, or want to create a new one, please contact us to get your rsync credentials.

Git Repository Mac Os X

https://mirrors.ukfast.co.uk/sites/gimp.org/pub/gimp/
ftp://mirrors.ukfast.co.uk/gimp.org/pub/gimp/
rsync://mirrors.ukfast.co.uk/gimp.org/pub/gimp/
Denmark
https://mirrors.dotsrc.org/gimp/gimp/
ftp://mirrors.dotsrc.org/gimp/
rsync://mirrors.dotsrc.org/gimp/
Finland
https://www.nic.funet.fi/pub/mirrors/ftp.gimp.org/
ftp://ftp.funet.fi/pub/mirrors/ftp.gimp.org/
rsync://rsync.nic.funet.fi/ftp/pub/mirrors/ftp.gimp.org/
France
http://ftp.iut-bm.univ-fcomte.fr/gimp/
ftp://ftp.iut-bm.univ-fcomte.fr/gimp/
rsync://ftp.iut-bm.univ-fcomte.fr/gimp/
Germany
https://ftp.fau.de/gimp/gimp/
ftp://ftp.fau.de/gimp/gimp/
rsync://ftp.fau.de/gimp/
https://ftp.gwdg.de/pub/misc/grafik/gimp/
ftp://ftp.gwdg.de/pub/misc/grafik/gimp/
https://artfiles.org/gimp.org/pub/gimp/
Greece
https://ftp.cc.uoc.gr/mirrors/gimp/
ftp://ftp.cc.uoc.gr/mirrors/gimp/
Japan
http://www.ring.gr.jp/pub/graphics/gimp/
Netherlands
https://ftp.snt.utwente.nl/pub/software/gimp/gimp/
ftp://ftp.snt.utwente.nl/pub/software/gimp/gimp/
Philippines
http://mirror.rise.ph/gimp/
ftp://mirror.rise.ph/gimp/
Poland
https://ftp.icm.edu.pl/pub/graphics/gimp/
ftp://ftp.icm.edu.pl/pub/graphics/gimp/
rsync://ftp.icm.edu.pl/pub/graphics/gimp/
gopher://ftp.icm.edu.pl/1/pub/graphics/gimp/
Sweden
https://ftp.lysator.liu.se/pub/gimp/
ftp://ftp.lysator.liu.se/pub/gimp
rsync://ftp.lysator.liu.se/pub/gimp
Ukraine
https://gimp.ip-connect.info/gimp/
rsync://gimp.ip-connect.info/gimp/
ftp://gimp.ip-connect.info/mirror/gimp/
https://mirror.klaus-uwe.me/gimp/gimp/
ftp://mirror.klaus-uwe.me/gimp/
rsync://mirror.klaus-uwe.me/gimp/
United Kingdom
https://www.mirrorservice.org/sites/ftp.gimp.org/pub/gimp/
ftp://ftp.mirrorservice.org/sites/ftp.gimp.org/pub/gimp/
rsync://rsync.mirrorservice.org/ftp.gimp.org/pub/gimp/
United States
https://mirror.jaleco.com/gimp/gimp/
https://mirror.umd.edu/gimp/gimp/
http://gimp.cp-dev.com/
ftp://devhost.cp-dev.com/gimp
rsync://gimp.cp-dev.com/gimp
https://mirrors.syringanetworks.net/gimp/gimp/
ftp://mirrors.syringanetworks.net/gimp/
rsync://mirrors.syringanetworks.net/gimp/
https://mirrors.xmission.com/gimp/gimp/
ftp://mirrors.xmission.com/gimp/gimp/