1. Can I Delete Diagnostic Reports On Mac Library Software
2. Can I Delete Diagnostic Reports On Mac Library Card
3. Can I Delete Diagnostic Reports On Mac Library Cardi

Similar to clearing cache and cleaning temporary files on a Mac, there is no practical benefit to deleting logs for the average Mac user and the vast majority should not do so. If you simply want to view logs, opening the Console app is generally a better approach. How to Clear User Logs from Mac OS.

If you've followed the steps to connect your Mac to a Wi-Fi network, but the connection to your network or the Internet isn't reliable, the steps in this article might help.

1. Alternatively you can also check the log files in /var/log (such as system.log), or in real-time by log stream. You can also check where dumps are generated by monitoring system.log file, e.g. Tail -f /var/log/system.log grep crash # Hit Control-C to stop. To scan for the previous crash files, run: grep crash /var/log/system.log.
2. Lion added Wi-Fi Diagnostics, but hid it away; it was largely intended to be used by AppleCare technicians or Apple Store Geniuses, who’d use it to generate detailed log reports.

Check for Wi-Fi recommendations

When your Mac tries to connect to a Wi-Fi network, it checks for issues that affect its ability to create a fast, stable and secure connection. If an issue is detected, the Wi-Fi status menu in the menu bar shows a new item: Wi-Fi Recommendations. Choose it to see recommended solutions.

Wi-Fi recommendations are available in macOS Sierra or later.

Analyse your wireless environment

Your Mac can use Wireless Diagnostics to perform additional analysis.

1. Quit any apps that are open, and connect to your Wi-Fi network, if possible.
2. Press and hold Option (Alt) ⌥ key, then choose Open Wireless Diagnostics from the Wi-Fi status menu .
3. Enter your administrator name and password when prompted.

Wireless Diagnostics begins analysing your wireless environment:

If the issue is intermittent, you can choose to monitor your Wi-Fi connection:

When you're ready to see recommendations, continue to the summary. Wireless Diagnostics asks for optional information about your base station or other router, so that it can include that in the report it saves to your Mac.

Click the info button next to each item in the summary to see details about that item. Wi-Fi best practices are tips that apply to most Wi-Fi networks.

Back up or make note of your network or router settings before changing them based on these recommendations — in case you need to use those settings again.

Monitor your Wi-Fi connection

Your Mac can monitor your Wi-Fi connection for intermittent issues, such as dropped connections. Follow the steps to analyse your wireless environment, but choose ”Monitor my Wi-Fi connection” when prompted.

During monitoring, a window shows that monitoring is in progress. Monitoring continues as long as this window is open and you're on the same Wi-Fi network, even when your Mac is asleep.

If Wireless Diagnostics finds an issue, it stops monitoring and shows a brief description of the issue. You can then resume monitoring or continue to the summary for details and recommendations.

Create a diagnostics report

Wireless Diagnostics automatically saves a diagnostics report before it displays its summary. You can create the same report at any time: press and hold the Option key, then choose Create Diagnostics Report from the Wi-Fi status menu . It can take your Mac several minutes to create the report.

• macOS Sierra and later saves the report to the /var/tmp folder of your startup drive, then opens that folder for you.
  To open the folder manually, choose Go > Go to Folder from the Finder menu bar, then enter /var/tmp.
• OS X El Capitan or earlier saves the report to your desktop.
  

The report is a compressed file with a name that begins “WirelessDiagnostics”. It contains many files that describe your wireless environment in detail. A network specialist can examine them for further analysis.

Use other diagnostics utilities

Wireless Diagnostics includes additional utilities for network specialists. Open them from the Window menu in the Wireless Diagnostics menu bar:

• Info gathers key details about your current network connections.
  
• Logs enables background logging for Wi-Fi and other system components. The result is saved to a .log file in the diagnostics report location on your Mac. Logging continues even when you quit the app or restart your Mac, so remember to disable logging when you're done.
  
• Scan finds Wi-Fi routers in your environment and gathers key details about them.
  
• Performance uses live graphs to show the performance of your Wi-Fi connection:
  • Rate shows the transmit rate over time in megabits per second.
  • Quality shows the signal-to-noise ratio over time. When the quality is too low, your device disconnects from the Wi-Fi router. Factors that affect quality include the distance between your device and the router, and objects such as walls that impede the signal from your router. Learn more.
  • Signal shows both signal (RSSI) and noise measurements over time. You want RSSI to be high and noise to be low, so the bigger the gap between RSSI and noise, the better.
• Sniffer captures traffic on your Wi-Fi connection, which can be useful when diagnosing a reproducible issue. Select a channel and width, then click Start to begin capturing traffic on that channel. When you click Stop, a .wcap file is saved to the diagnostics report location on your Mac.

Learn more

Additional recommendations for best Wi-Fi performance:

• Keep your router up to date. For AirPort Time Capsule, AirPort Extreme or AirPort Express Base Station, check for the latest firmware using AirPort Utility. For non-Apple routers, check the manufacturer's website.
• Set up your router using Apple's recommended settings, and make sure that all Wi-Fi routers on the same network use similar settings.If you're using a dual-band Wi-Fi router, make sure that both bands use the same network name.
• Learn about potential sources of Wi-Fi and Bluetooth interference.

Learn about other ways to connect to the Internet.

Estimated reading time: 16 minutes

Did you know that Docker Desktop now offers support for developers subscribed to a Pro or a Team plan? Click here to learn more.

This page contains information on how to diagnose and troubleshoot Docker Desktop issues, request Docker Desktop support (Pro and Team plan users only), send logs and communicate with the Docker Desktop team, use our forums and Success Center, browse and log issues on GitHub, and find workarounds for known problems.

Troubleshoot

Choose > Troubleshootfrom the menu bar to see the troubleshoot options.

The Troubleshoot page contains the following options:

• Restart Docker Desktop: Select to restart Docker Desktop.

• Support: Developers on Pro and Team plans can use this option to send a support request. Other users can use this option to diagnose any issues in Docker Desktop. For more information, see Diagnose and feedback and Support.

• Reset Kubernetes cluster: Select this option to delete all stacks and Kubernetes resources. For more information, see Kubernetes.

• Clean / Purge data: This option resets all Docker data without areset to factory defaults. Selecting this option results in the loss of existing settings.

• Reset to factory defaults: Choose this option to reset all options onDocker Desktop to their initial state, the same as when Docker Desktop was first installed.

• Uninstall: Choose this option to remove Docker Desktop from yoursystem.

Uninstall Docker Desktop from the command line

To uninstall Docker Desktop from a terminal, run: <DockerforMacPath>--uninstall. If your instance is installed in the default location, thiscommand provides a clean uninstall:

You might want to use the command-line uninstall if, for example, you find thatthe app is non-functional, and you cannot uninstall it from the menu.

Diagnose and feedback

In-app diagnostics

If you encounter problems for which you do not find solutions in thisdocumentation, on Docker Desktop issues onGitHub, or the Docker Desktop forum, we can help you troubleshootthe log data. Before reporting an issue, we recommend that you read the information provided on this page to fix some common known issues.

Note

Docker Desktop offers support for users subscribed to a Pro or a Team plan. If you are experiencing any issues with Docker Desktop, follow the instructions in this section to send a support request to Docker Support.

Before you get started, we recommend that you sign into your Docker Desktop application and your Docker Hub account.

1. Choose > Troubleshoot.
2. Sign into Docker Desktop. In addition, ensure you are signed into your Docker account.
3. Click Get support. This opens the in-app Support page and starts collecting the diagnostics.
4. When the diagnostics collection process is complete, click Upload to get a Diagnostic ID.
5. When the diagnostics have been uploaded, Docker Desktop prints a diagnostic ID. Copy this ID.
6. If you have subscribed to a Pro or a Team plan, click Contact Support. This opens the Docker Desktop support form. Fill in the information required and add the ID you copied earlier to the Diagnostics ID field. Click Submit to request Docker Desktop support.

   Note

   You must be signed in to Docker Desktop using your Pro or Team plan credentials to access the support form. For information on what’s covered as part of Docker Desktop support, see Support.

7. If you are not subscribed to a Pro or a team plan, you can click Upgrade to benefit from Docker Support to upgrade your existing account. Alternatively, click Report a Bug to open a new Docker Desktop issue on GitHub. This opens Docker Desktop for Mac on GitHub in your web browser in a ‘New issue’ template. Complete the information required and ensure you add the diagnostic ID you copied earlier. Click submit new issue to create a new issue.

Diagnosing from the terminal

In some cases, it is useful to run the diagnostics yourself, for instance, ifDocker Desktop cannot start.

First, locate the com.docker.diagnose tool. If you have installed Docker Desktop in the Applications directory, then it is located at/Applications/Docker.app/Contents/MacOS/com.docker.diagnose.

To create and upload diagnostics, run:

After the diagnostics have finished, you should have the following output,containing your diagnostics ID:

The diagnostics ID (here BE9AFAAF-F68B-41D0-9D12-84760E6B8740/20190905152051) iscomposed of your user ID (BE9AFAAF-F68B-41D0-9D12-84760E6B8740) and a timestamp(20190905152051). Ensure you provide the full diagnostics ID, and not just the user ID.

To view the contents of the diagnostic file, run:

Check the logs

In addition to using the diagnose and feedback option to submit logs, you canbrowse the logs yourself.

In a terminal

To watch the live flow of Docker Desktop logs in the command line, run the following script from your favorite shell.

Alternatively, to collect the last day of logs (1d) in a file, run:

In the Console app

Macs provide a built-in log viewer, named “Console”, which you can use to checkDocker logs.

The Console lives in /Applications/Utilities; you can search for it withSpotlight Search.

To read the Docker app log messages, type docker in the Console window search bar and press Enter. Then select ANY to expand the drop-down list next to your docker search entry, and select Process.

You can use the Console Log Query to search logs, filter the results in variousways, and create reports.

Troubleshooting

Make sure certificates are set up correctly

Docker Desktop ignores certificates listed under insecure registries, and doesnot send client certificates to them. Commands like docker run that attempt topull from the registry produces error messages on the command line, for example:

As well as on the registry. For example:

For more about using client and server side certificates, seeAdding TLS certificates in the Getting Started topic.

Volume mounting requires file sharing for any project directories outside of /Users

If you are using mounted volumes and get runtime errors indicating anapplication file is not found, access to a volume mount is denied, or a servicecannot start, such as when using Docker Compose,you might need to enable file sharing.

Volume mounting requires shared drives for projects that live outside of the/Users directory. Go to >Preferences > Resources > File sharing and share the drive that contains the Dockerfile and volume.

Incompatible CPU detected

Docker Desktop requires a processor (CPU) that supports virtualization and, morespecifically, the Apple Hypervisorframework.Docker Desktop is only compatible with Mac systems that have a CPU that supports the Hypervisor framework. Most Macs built in 2010 and later support it,as described in the Apple Hypervisor Framework documentation about supported hardware:

Generally, machines with an Intel VT-x feature set that includes Extended PageTables (EPT) and Unrestricted Mode are supported.

To check if your Mac supports the Hypervisor framework, run the following command in a terminal window.

If your Mac supports the Hypervisor Framework, the command printskern.hv_support: 1.

If not, the command prints kern.hv_support: 0.

See also, Hypervisor FrameworkReferencein the Apple documentation, and Docker Desktop Mac system requirements.

Workarounds for common problems

• If Docker Desktop fails to install or start properly on Mac:

  • Make sure you quit Docker Desktop before installing a new version of theapplication ( > Quit Docker Desktop). Otherwise, you get an “application in use” error when you try tocopy the new app from the .dmg to /Applications.

  • Restart your Mac to stop / discard any vestige of the daemon running fromthe previously installed version.

  • Run the uninstall commands from the menu.

• If docker commands aren’t working properly or as expected, you may need tounset some environment variables, to make sure you are not using the legacyDocker Machine environment in your shell or command window. Unset theDOCKER_HOST environment variable and related variables. If you use bash, use the following command: unset ${!DOCKER_*}

• For the hello-world-nginx example, Docker Desktop must be running to get tothe web server on http://localhost/. Make sure that the Docker icon isdisplayed on the menu bar, and that you run the Docker commands in a shell that is connected to the Docker Desktop Engine.Otherwise, you might start the webserver container but get a “web page notavailable” error when you go to localhost.

• If you see errors like Bind for 0.0.0.0:8080 failed: port is alreadyallocated or listen tcp:0.0.0.0:8080: bind: address is already in use:

  • These errors are often caused by some other software on the Mac using thoseports.

  • Run lsof -i tcp:8080 to discover the name and pid of the other process anddecide whether to shut the other process down, or to use a different port inyour docker app.

Known issues

Can I Delete Diagnostic Reports On Mac Library Software

• The following issues are seen when using the virtualization.framework experimental feature:

  • Some VPN clients can prevent the VM running Docker from communicating with the host, preventing Docker Desktop starting correctly. See docker/for-mac#5208.

    This is an interaction between vmnet.framework (as used by virtualization.framework in Big Sur) and the VPN clients.

  • Docker Desktop is incompatible with macOS Internet Sharing. See docker/for-mac#5348.

    This is an interaction between vmnet.framework (as used by virtualization.framework in Big Sur) and macOS Internet Sharing. At the moment it is not possible to use Docker Desktop and macOS Internet Sharing at the same time.

  • Some container disk I/O is much slower than expected. See docker/for-mac#5389. Disk flushes are particularly slow due to the need to guarantee data is written to stable storage on the host.

    This is an artifact of the new virtualization.framework in Big Sur.

  • TCP and UDP port 53 (DNS) are bound on the host when Docker Desktop starts. Therefore you cannot bind to port 53 on all interfaces with a command like docker run -p 53:53. See docker/for-mac#5335.

    This is an artifact of the new virtualization.framework in Big Sur. A workaround is to bind to a specific IP address e.g. docker run -p 127.0.0.1:53:53.

  • The Linux Kernel may occasionally crash. Docker now detects this problem and pops up an error dialog offering the user the ability to quickly restart Linux.

    We are still gathering data and testing alternate kernel versions.

• IPv6 is not (yet) supported on Docker Desktop.

• You might encounter errors when using docker-compose up with Docker Desktop(ValueError: Extra Data). We’ve identified this is likely related to dataand/or events being passed all at once rather than one by one, so sometimesthe data comes back as 2+ objects concatenated and causes an error.

• Force-ejecting the .dmg after running Docker.app from it can cause thewhale icon to become unresponsive, Docker tasks to show as not responding inthe Activity Monitor, and for some processes to consume a large amount of CPUresources. Reboot and restart Docker to resolve these issues.

• Docker does not auto-start on login even when it is enabled in > Preferences. This is related to aset of issues with Docker helper, registration, and versioning.

• Docker Desktop uses the HyperKit hypervisor(https://github.com/docker/hyperkit) in macOS 10.10 Yosemite and higher. Ifyou are developing with tools that have conflicts with HyperKit, such asIntel Hardware Accelerated Execution Manager(HAXM),the current workaround is not to run them at the same time. You can pauseHyperKit by quitting Docker Desktop temporarily while you work with HAXM.This allows you to continue work with the other tools and prevent HyperKitfrom interfering.

• If you are working with applications like ApacheMaven that expect settings for DOCKER_HOST andDOCKER_CERT_PATH environment variables, specify these to connect to Dockerinstances through Unix sockets. For example:

• There are a number of issues with the performance of directories bind-mountedinto containers. In particular, writes of small blocks, and traversals of largedirectories are currently slow. Additionally, containers that perform largenumbers of directory operations, such as repeated scans of large directorytrees, may suffer from poor performance. Applications that behave in this wayinclude:

  • rake
  • ember build
  • Symfony
  • Magento
  • Zend Framework
  • PHP applications that use Composer to installdependencies in a vendor folder
    

  As a workaround for this behavior, you can put vendor or third-party librarydirectories in Docker volumes, perform temporary file system operationsoutside of bind mounts, and use third-party tools like Unison or rsync tosynchronize between container directories and bind-mounted directories. We areactively working on performance improvements using a number of differenttechniques. To learn more, see the topic on our roadmap.

Support

Docker Desktop offers support for developers subscribed to a Pro or a Team plan. Click here to upgrade your existing account.

This section contains instructions on how to get support, and covers the scope of Docker Desktop support.

How do I get Docker Desktop support?

If you have subscribed to a Pro and Team account, please raise a ticket through Docker Desktop support.

Docker Community users can get support through our Github repos for-win and for-mac, where we respond on a best-effort basis.

What support can I get?

If you are a Pro or a Team user, you can request for support on the following types of issues:

• Desktop upgrade issues
• Desktop installation issues
  • Installation crashes
  • Failure to launch Docker Desktop on first run
• Usage issues
  • Crash closing software
  • Docker Desktop not behaving as expected
• Configuration issues
• Basic product ‘how to’ questions

What is not supported?

Docker Desktop excludes support for the following types of issues:

• Use on or in conjunction with hardware or software other than that specified in the applicable documentation
• Running on unsupported operating systems, including beta/preview versions of operating systems
• Running containers of a different architecture using emulation
• Support for the Docker engine, Docker CLI, or other bundled Linux components
• Support for Kubernetes
• Features labeled as experimental
• System/Server administration activities
• Supporting Desktop as a production runtime
• Scale deployment/multi-machine installation of Desktop
• Routine product maintenance (data backup, cleaning disk space and configuring log rotation)
• Third-party applications not provided by Docker
• Altered or modified Docker software
• Defects in the Docker software due to hardware malfunction, abuse, or improper use
• Any version of the Docker software other than the latest version
• Reimbursing and expenses spent for third-party services not provided by Docker
• Docker Support excludes training, customization, and integration

What versions are supported?

We currently only offer support for the latest version of Docker Desktop. If you are running an older version, you may be asked to upgrade before we investigate your support request.

How many machines can I get support for Docker Desktop on?

As a Pro user you can get support for Docker Desktop on a single machine.As a Team, you can get support for Docker Desktop for the number of machines equal to the number of seats as part of your plan.

What OS’s are supported?

Docker Desktop is available for Mac and Windows. The supported version information can be found on the following pages:

Can I Delete Diagnostic Reports On Mac Library Card

Can I run Docker Desktop on Virtualized hardware?

Can I Delete Diagnostic Reports On Mac Library Cardi

No, currently this is unsupported and against the terms of use.