docker buildx create --use
docker buildx build --platform linux/arm64/v8,linux/amd64 . -t foo:latest --push
# kube get pod logs by pod name | |
function podlogs() { | |
k logs -f $(k get pods | grep "$1" | cut -d ' ' -f 1) | |
} |
kubectl set image deployment/my-deployment app=myimage |
List base image names and tags
curl https://docker.example.com/v2/_catalog. # List repos (base image names)
curl https://docker.example.com/v2/myimage/tags/list # List image tags
Ok for image names to have forward slashes
To get all images in a registry, call the catalog API, then call tags/list for each result.
Source: https://wiki.teltonika-networks.com/view/Mobile_Signal_Strength_Recommendations | |
RSRP | |
RSRP Signal strength Description | |
>= -80 dBm Excellent Strong signal with maximum data speeds | |
-80 dBm to -90 dBm Good Strong signal with good data speeds | |
-90 dBm to -100 dBm Fair to poor Reliable data speeds may be attained, but marginal data with drop-outs is possible. When this value gets close to -100, performance will drop drastically | |
<= -100 dBm No signal Disconnection | |
RSRQ |
kubectl cp production/my-pod-77d5978bbd-hlmzb:/app/output.csv output.csv |
Use UPDATE SKIP LOCKED
to manage queue concurrency
DELETE FROM queue
WHERE itemid = (
SELECT itemid
FROM queue
ORDER BY itemid
FOR UPDATE SKIP LOCKED
LIMIT 1
8.2.2. TCP log format | |
--------------------- | |
The TCP format is used when "option tcplog" is specified in the frontend, and | |
is the recommended format for pure TCP proxies. It provides a lot of precious | |
information for troubleshooting. Since this format includes timers and byte | |
counts, the log is normally emitted at the end of the session. It can be | |
emitted earlier if "option logasap" is specified, which makes sense in most | |
environments with long sessions such as remote terminals. Sessions which match | |
the "monitor" rules are never logged. It is also possible not to emit logs for |
tmux movew -r