On M1 machines, Docker for Mac is running a lightweight linux ARM VM, then running containers within that, so containers are essentially running natively. Don't be fooled by the fact the UI or binary CLI tools (e.g. docker
) might require Rosetta.
Within that VM is an emulation layer called QEmu. This can be used by docker to run Intel containers. This does not use Rosetta at all, and has a roughly 5-6X performance penalty. (If you just upgraded your CPU this may result in a similar performance to your old machine!)
Many images in public registries are multi-architecture. For instance at the time of writing on Docker Hub the php:8.0-cli
image has the following digests:
# install pygit2: pip install pygit2 | |
import pygit2 | |
import json | |
repo = pygit2.Repository('path/to/repository') | |
last = repo[repo.head.target] | |
data = [] | |
for commit in repo.walk(last.id): |
<?php | |
# In-place apply the CVE-2020-15227 nette/application patch | |
# This is a universal patcher for all affected versions. | |
# Run with `php patch-CVE-2020-15227.php` | |
# Inspiration: @spazef0rze | |
#!/bin/bash | |
# Find files in CVE-2020-15227 nette/application issue | |
# by @spazef0rze | |
# Run with `bash find-cve-2020-15227.sh`, works on Linux, FreeBSD, tested on Ubuntu 18.04, FreeBSD 11.4 | |
# This is a universal finder for all affected versions. | |
# Requirements: find, grep, bash (might work with your default shell but YMMV) | |
# The fixes: |
Azure AD MFA is not enabled by default for AAD and Microsoft 365 users, but it will be if during setup an admin chooses to Enable Security Defaults on Azure AD (as most will when prompted to do so: after all, who in their right mind wouldn't require MFA?).
However, there are situations where being able to toggle MFA on or off for a particular user can be useful. For example, in a development or test tenant when working with sample code from Microsoft that doesn't account for MFA (like a simple Microsoft Graph console app). This procedure involves disabling Security Defaults on AAD.
variable "worker_names" { | |
type = "list" | |
} | |
# worker_names = [ | |
# "w1", | |
# "w2", | |
# "w3", | |
# ] |
Registering Rancher managed clusters in Argo CD doesn't work out of the box unless the Authorized Cluster Endpoint is used. Many users will prefer an integration of Argo CD via the central Rancher authentication proxy (which shares the network endpoint of the Rancher API/GUI). So let's find out why registering clusters via Rancher auth proxy fails and how to make it work.
Hint: If you are just looking for the solution scroll to the bottom of this page.
*.0.devklarka.cz | |
*.05.cz | |
*.0e.cz | |
*.0oo.cz | |
*.1.devklarka.cz | |
*.10.devklarka.cz | |
*.1001hry.cz | |
*.100letvyroci.cz | |
*.100py.cz | |
*.11.devklarka.cz |
Rust error handling is nice but obligatory. Which makes it sometimes plenty of code.
Functions return values of type Result that is "enumeration". In Rust enumeration means complex value that has alternatives and that alternative is shown with a tag.
Result is defined as Ok or Err. The definition is generic, and both alternatives have