#docker tag image

[codeonedigest]

Docker Tag and Push Image to Hub | Docker Tagging Explained and Best Practices

Full Video Link: https://youtu.be/X-uuxvi10Cw Hi, a new #video on #DockerImageTagging is published on @codeonedigest #youtube channel. Learn TAGGING docker image. Different ways to TAG docker image #Tagdockerimage #pushdockerimagetodockerhubrepository #

Next step after building the docker image is to tag docker image. Image tagging is important to upload docker image to docker hub repository or azure container registry or elastic container registry etc. There are different ways to TAG docker image. Learn how to tag docker image? What are the best practices for docker image tagging? How to tag docker container image? How to tag and push docker…

[gender-trash]

do you guys know about "i now make furniture out of wood" because this plays in my head every time i open my work laptop and am immediately besieged by questions

[bluntblade]

10 Fandoms, 10 Characters, 10 Tags

Thank you to @sinvulkt for the tag :D Let's go...

Rey (Star Wars Sequels)

Rey is at this stage by some way the character I've spilled the most ink over, specifically a post-TLJ Rey Nobody. I love her curiosity, her loyalty and that core of wounded anger. I want her to be happy and kick baddies in the head.

2. Ikrie (Horizon: Forbidden West)

Shape a woman out of abandonment issues and give her a spear. With so little screentime, she's such a fully-formed character, tough yet vulnerable, flitting between rambunctious and melancholy, and "I never cared about the Werak" cuts me to the bone each time.

3. Shiban Khan (The Horus Heresy)

Broken down and built back up, two or three times over. It's heartbreaking to see how he falls into bitterness over the course of the Heresy, and then glorious to see him rise again and become one of his Legion's greatest heroes.

4. Barristan Selmy (A Song of Ice and Fire)

It's fascinating to watch a character shaking off decades of swallowed doubts, forced to evolve by events. If we ever get The Winds of Winter, I hope his progression continues.

5. Keeve Trennis (Star Wars: The High Republic)

Adorable, great haircut, bold and passionate yet warring with impostor syndrome. Also swears like a Corellian kriffing docker, and she has a neat splitting saberstaff. What's not to love?

6. Theoden (The Lord of the Rings)

It still amazes me upon rewatching The Two Towers that Bernard Hill doesn't just walk off with the whole film, his performance is so magnificent. I don't think there's really anything I can add which hasn't been said already.

7. Caitlyn Kirramen (Arcane)

Lawful good, beginning to realise just how how questionable the good of the law she serves is. Her evolving dynamic with Vi is great, she's tougher than those around her expect and of course, she's so very very pretty.

8. Stephen Maturin (Master and Commander)

A canny spy who is nonetheless perpetually baffled and exasperated by the nautical world he has inveigled himself into. Also a thorough nerd.

9. Mahit Dzmare & Three Seagrass (A Memory Called Empire & A Desolation Called Peace)

Cheating a little in part because I couldn't find a solo pic of Mahit that wasn't AI-generated and also because I love them so very much, your honour. These little bundles of anxiety and constant second-guessing, pitched into events far more massive and momentous than anything either had imagined. And they have moments of intimacy to eat rocks for.

10. Yrica Quell (Star Wars: Alphabet Squadron)

You can fit so much guilt and conflict in this bad girl. Quell has arguably the most fascinating "Imperial defector" arc in all the Star Wars media I've read, as she undergoes this evolving moral struggle across her trilogy.

No-pressure tagging @mehoymalloy, @foibles-fables, @meg-noel-art, @dino-trash-kieran, @iron-shrike, @retrob0t, @fancyfrey, @tremendouskoalachild, @robo-dino-puppy and @lilypuffsw

[labexio]

Understanding Docker Playground Online: Your Gateway to Containerization

In the ever-evolving world of software development, containerization has become a pivotal technology, allowing developers to create, deploy, and manage applications in isolated environments. Docker, a leader in this domain, has revolutionized how applications are built and run. For both novices and seasoned developers, mastering Docker is now essential, and one of the best ways to do this is by leveraging an Online Docker Playground. In this article, we will explore the benefits of using such a platform and delve into the Docker Command Line and Basic Docker Commands that form the foundation of containerization.

The Importance of Docker in Modern Development

Docker has gained immense popularity due to its ability to encapsulate applications and their dependencies into containers. These containers are lightweight, portable, and can run consistently across different computing environments, from a developer's local machine to production servers in the cloud. This consistency eliminates the "it works on my machine" problem, which has historically plagued developers.

As a developer, whether you are building microservices, deploying scalable applications, or managing a complex infrastructure, Docker is an indispensable tool. Understanding how to effectively use Docker begins with getting comfortable with the Docker Command Line Interface (CLI) and mastering the Basic Docker Commands.

Learning Docker with an Online Docker Playground

For beginners, diving into Docker can be daunting. The Docker ecosystem is vast, with numerous commands, options, and configurations to learn. This is where an Online Docker Playground comes in handy. An Online Docker Playground provides a sandbox environment where you can practice Docker commands without the need to install Docker locally on your machine. This is particularly useful for those who are just starting and want to experiment without worrying about configuring their local environment.

Using an Online Docker Playground offers several advantages:

Accessibility: You can access the playground from any device with an internet connection, making it easy to practice Docker commands anytime, anywhere.

No Installation Required: Skip the hassle of installing Docker and its dependencies on your local machine. The playground provides a ready-to-use environment.

Safe Experimentation: You can test commands and configurations in a risk-free environment without affecting your local system or production environment.

Immediate Feedback: The playground often includes interactive tutorials that provide instant feedback, helping you learn more effectively.

Getting Started with Docker Command Line

The Docker Command Line Interface (CLI) is the primary tool you'll use to interact with Docker. It's powerful, versatile, and allows you to manage your Docker containers and images with ease. The CLI is where you will issue commands to create, manage, and remove containers, among other tasks.

To begin, let's explore some Basic Docker Commands that you will frequently use in your journey to mastering Docker:

docker run: This command is used to create and start a new container from an image. For example, docker run hello-world pulls the "hello-world" image from Docker Hub and runs it in a new container.

docker ps: To see a list of running containers, use the docker ps command. To view all containers (running and stopped), you can add the -a flag: docker ps -a.

docker images: This command lists all the images stored locally on your machine. It shows details like the repository, tag, image ID, and creation date.

docker pull: To download an image from Docker Hub, use docker pull. For example, docker pull nginx fetches the latest version of the NGINX image from Docker Hub.

docker stop: To stop a running container, use docker stop [container_id]. Replace [container_id] with the actual ID or name of the container you want to stop.

docker rm: Once a container is stopped, you can remove it using docker rm [container_id].

docker rmi: If you want to delete an image from your local storage, use docker rmi [image_id].

Conclusion

Mastering Docker is a crucial skill for modern developers, and utilizing an Online Docker Playground is one of the most effective ways to get started. By practicing Docker Command Line usage and familiarizing yourself with Basic Docker Commands, you can gain the confidence needed to manage complex containerized environments. As you progress, you'll find that Docker not only simplifies the deployment process but also enhances the scalability and reliability of your applications. Dive into Docker today, and unlock the full potential of containerization in your development workflow.

[tutorialsfor]

Fundamentals of Docker for Beginners - Learn Docker from Scratch - Saifosys.com by TutorialsFor #dockertutorials #dockerforbeginners #learndocker Unlock the power of containerization! 🚀 Learn the fundamentals of Docker in this beginner-friendly tutorial. Discover how to simplify your development workflow, improve app deployment, and increase efficiency. In this video, we'll cover: - Comparison of Traditional approach vs Virtualization vs Containerization https://ift.tt/wH9K5dp - Docker basics: Docker Architecture https://ift.tt/jPrafFd What is Docker Daemon? What is Docker Client ? What is Docker Registry ? What is Docker Host ? What is Docker Images ? What is Docker Container ? How to Install Docker on Windows How to Create account on Docker hub How to pull the images from Docker Hub How to Run images and create containers How to list the containers How to list images How to go inside container How to stop container How to start container How remove container How to remove images https://ift.tt/Tl0w6k9 How to build docker image from dockerfile How to run docker image and create container locally How to tag docker images How to push docker images to docker hub registry How to verify the published docker images on docker hub https://ift.tt/08mvztC Perfect for developers, DevOps engineers, and anyone curious about Docker! 💻 Watch now and start containerizing your future! #DockerForBeginners #Containerization #DevOps #DockerTutorial" - #DockerTutorial - #Containerization - #DevOps - #DockerBasics - #DockerTraining - #CloudComputing - #Virtualization - #TechTutorial - #DockerContainers - #DockerImages - #Dockerfile - #DockerHub https://www.youtube.com/watch?v=398al57gwaQ

[qcs01]

Containerization with Docker and Kubernetes: An Essential Guide

Docker and Kubernetes have emerged as foundational tools for containerization and orchestration in the rapidly evolving landscape of cloud-native technologies. This blog post explores their roles, provides setup guides, and highlights key use cases demonstrating their power and flexibility.

Introduction to Containerization

Containerization is a lightweight alternative to traditional virtualization, enabling applications to run in isolated environments. This approach solves many problems related to environment consistency, application deployment, and scalability. 

Docker: The Containerization Pioneer

What is Docker?

Docker is an open-source platform that automates the deployment of applications inside lightweight, portable containers. It encapsulates an application and its dependencies, ensuring it runs consistently across various environments.

Why Use Docker?

Consistency: Ensures the application behaves the same, regardless of where it is run.

Efficiency: Reduces overhead by sharing the host OS kernel.

Portability: Facilitates seamless movement of applications between development, testing, and production environments.

Setting Up Docker

1. Install Docker:

   - Windows & macOS: Download the Docker Desktop installer from [Docker's official site](https://www.docker.com/products/docker-desktop).

   - Linux: Use the package manager. For example, on Ubuntu:

     sudo apt-get update

     sudo apt-get install docker-ce docker-ce-cli containerd.io

2. Verify Installation:

 docker --version

3. Run Your First Container:

    docker run hello-world

Docker Use Cases

- Microservices: Simplifies the deployment and management of microservice architectures.

- DevOps: Streamlines CI/CD pipelines by providing consistent environments.

- Hybrid Cloud: Enables seamless movement of workloads between on-premises and cloud environments.

Kubernetes: Orchestrating Containers at Scale

What is Kubernetes?

Kubernetes, often abbreviated as K8s, is an open-source platform for automating the deployment, scaling, and operation of containerized applications. It manages clusters of containers, ensuring high availability and scalability.

Why Use Kubernetes?

- Scalability: Automatically scales applications based on demand.

- Self-Healing: Automatically restarts, replaces, and reschedules containers when they fail.

- Service Discovery & Load Balancing: Efficiently balances traffic and discovers services without manual intervention.

Setting Up Kubernetes

1. Install Kubernetes Tools:

   - kubectl: Command-line tool for interacting with Kubernetes clusters.

   - Minikube: Local Kubernetes cluster for development.

   # Install kubectl

   sudo apt-get update

   sudo apt-get install -y kubectl

    Install Minikube

   curl -Lo minikube https://storage.googleapis.com/minikube/releases/latest/minikube-linux-amd64

   chmod +x minikube

   sudo mv minikube /usr/local/bin/

2. Start Minikube:

  minikube start

3. Deploy an Application:

   kubectl create deployment hello-node --image=k8s.gcr.io/echoserver:1.4

   kubectl expose deployment hello-node --type=LoadBalancer --port=8080

   minikube service hello-node

Kubernetes Use Cases

- Complex Applications: Manages applications with multiple, interdependent services.

- CI/CD Pipelines: Enhances automation and reduces the risk of deployment issues.

- Multi-Cloud Deployments: Orchestrates applications across various cloud providers.

Integrating Docker and Kubernetes

While Docker provides the containerization platform, Kubernetes offers robust orchestration capabilities. Together, they form a powerful combination for building, deploying, and managing cloud-native applications.

Example Workflow:

1. Build Docker Image:

   docker build -t my-app .

2. Push to Container Registry:

   docker tag my-app my-repo/my-app

   docker push my-repo/my-app

3. Deploy with Kubernetes:

   kubectl create deployment my-app --image=my-repo/my-app

   kubectl expose deployment my-app --type=LoadBalancer --port=80

Conclusion

Containerization with Docker and Kubernetes revolutionizes how applications are developed, deployed, and managed. By leveraging Docker's simplicity and Kubernetes' powerful orchestration capabilities, organizations can achieve greater agility, scalability, and reliability in their cloud-native journey.

For more details click www.hawkstack.com 

[sandeep2363]

Steps to deploy the docker latest image in AWS

To deploy the latest image in AWS, you typically follow these general steps: Create or Update Your Docker Image: Ensure that you have the latest version of your Docker image ready. This might involve pulling the latest changes from your code repository, building a new image, and tagging it appropriately with a version number or tag like “latest”. Once your Docker image is ready, push it to a…

[kubernetesonline]

Docker and Kubernetes Training | Hyderabad

How to Store Images in Container Registries?

Introduction:

Container registries serve as central repositories for storing and managing container images, facilitating seamless deployment across various environments. However, optimizing image storage within these registries requires careful consideration of factors such as scalability, security, and performance. - Docker and Kubernetes Training

Choose the Right Registry:

Selecting the appropriate container registry is the first step towards efficient image storage. Popular options include Docker Hub, Google Container Registry (GCR), Amazon Elastic Container Registry (ECR), and Azure Container Registry (ACR). Evaluate factors such as integration with existing infrastructure, pricing, security features, and geographical distribution to make an informed decision.

Image Tagging Strategy:

Implement a robust tagging strategy to organize and manage container images effectively. Use semantic versioning or timestamp-based tagging to denote image versions and updates clearly. Avoid using generic tags like "latest," as they can lead to ambiguity and inconsistent deployments. - Kubernetes Online Training

Optimize Image Size:

Minimize image size by adhering to best practices such as using lightweight base images, leveraging multi-stage builds, and optimizing Dockerfiles. Removing unnecessary dependencies and layers helps reduce storage requirements and accelerates image pull times during deployment.

Security Considerations:

Prioritize security by implementing access controls, image signing, and vulnerability scanning within the container registry. Restrict image access based on user roles and permissions to prevent unauthorized usage. Regularly scan images for vulnerabilities and apply patches promptly to mitigate potential risks. - Docker Online Training

Automated Builds and CI/CD Integration:

Integrate container registries with continuous integration/continuous deployment (CI/CD) pipelines to automate image builds, testing, and deployment processes. Leverage tools like Jenkins, GitLab CI/CD, or GitHub Actions to streamline workflows and ensure consistent image updates across environments.

Content Trust and Image Signing:

Enable content trust mechanisms such as Docker Content Trust or Notary to ensure image authenticity and integrity. By digitally signing images and verifying signatures during pull operations, organizations can mitigate the risk of tampering and unauthorized modifications.

Data Backup and Disaster Recovery:

Implement robust backup and disaster recovery strategies to safeguard critical container images against data loss or corruption. Regularly backup registry data to redundant storage locations and establish procedures for swift restoration in the event of failures or disasters. - Docker and Kubernetes Online Training

Performance Optimization:

Optimize registry performance by leveraging caching mechanisms, content delivery networks (CDNs), and geo-replication to reduce latency and improve image retrieval speeds. Distribute registry instances across multiple geographical regions to enhance availability and resilience.

Conclusion:

By following best practices such as selecting the right registry, optimizing image size, enforcing security measures, and integrating with CI/CD pipelines, organizations can streamline image management and enhance their containerized deployments without diving into complex coding intricacies.

Visualpath is the Leading and Best Institute for learning Docker And Kubernetes Online in Ameerpet, Hyderabad. We provide Docker Online Training Course, you will get the best course at an affordable cost.

Attend Free Demo

Call on - +91-9989971070.

Visit : https://www.visualpath.in/DevOps-docker-kubernetes-training.html

Blog : https://dockerandkubernetesonlinetraining.blogspot.com/

[myprogrammingsolver]

Homework #3: Docker container/image commands

Problem 1. Search the Docker Registry Use the CLI to search for “nginx” images and show the output (include the docker command you used). Filter to show only official “nginx” images and show the output (include the docker command you used). Problem 2. List Tags for an image Hit the following url in a browser, curl, or wget: https://registry.hub.docker.com/v1/repositories/nginx/tags (Links to an…

[startexport]

@node

Docker Official Image • 1B+ • 10K+ Node.js is a JavaScript-based platform for server-side and networking applications. docker pull node OverviewTags Quick reference Maintained by:The Node.js Docker Team Where to get help:the Docker Community Slack, Server Fault, Unix & Linux, or Stack Overflow Supported tags and…

[hydrus]

Version 556

windows

zip

exe

macOS

app

linux

tar.zst

I had an ok week. I fixed some bugs and added a system to force-set filetypes.

You will be asked on update if you want to regenerate some animation thumbnails. The popup explains the decision, I recommend 'yes'.

full changelog

forced filetype

The difference between a zip and an Ugoira and a cbz is not perfectly clear cut. I am happy with the current filetype scanner--and there are a couple more improvements this week--but I'm sure there will always be some fuzziness in the difficult cases. This also applies to some clever other situations, like files that secretly store a zip concatenated after a jpeg. You might want that file to be considered something other than hydrus thinks it technically is.

So, on any file selection, you can now hit right-click->manage->force filetype. You can set any file to be seen as any other file. The changes take affect immediately, are reflected in presentation and system:filetype searches, and the files themselves will be renamed on disk (to aid 'open externally'). The original filetype is remembered, and everything is easily undoable through the same dialog.

Also added is 'system:has forced filetype', under the 'system:file properties' entry, if you'd like to find what you have set one way or the other.

This is experimental, and I don't recommend it for the most casual users, but if you are comfortable, have a play with it. I still need to write better error handling for complete nonsense cases (e.g. calling a webm a krita is probably going to raise an error somewhere), but let me know how you get on.

other highlights

I fixed some dodgy numbers in Mr. Bones (deleted file count) and the file history chart (inbox/archive count). If you have had some whack results here, let me know if things are any better! If they aren't, does changing the search to something more specific than 'all my files'/'system:everything' improve things?

Some new boot errors, mostly related to missing database components, are now handled with nicer dialog prompts, and even interactive console prompts serverside.

I _may_ have fixed/relieved the 'program is hung when restored from minimise to system tray' issue, but I am not confident. If you still have this, let me know how things are now. If you still get a hang, more info on what your client was doing during the minimise would help--I just cannot reproduce this problem reliably.

Thanks to a user who figured out all the build script stuff, the Docker package is now Alpine 3.19. The Docker package should have newer libraries and broader file support.

birthday and year summary

The first non-experimental beta of hydrus was released on December 14th, 2011. We are now going on twelve years.

Like many, I had an imperfect 2023. I've no complaints, but IRL problems from 2022 cut into my free time and energy, and I regret that it impacted my hydrus work time. I had hoped to move some larger projects forward this year, but I was mostly treading water with little features and optimisations. That said, looking at the changelog for the year reveals good progress nonetheless, including: multiple duplicate search and filter speed and accuracy improvements, and the 'one file in this search, the other in this search' system; significant Client API expansions, in good part thanks to a user, including the duplicates system, more page inspections, multiple local file domains, and http headers; new sidecar datatypes and string processing tools; improvements to 'related tags' search; much better transparency support, including 'system:has transparency'; more program stability, particularly with mpv; much much faster tag autocomplete results, and faster tag and file search cancelling; the inc/dec rating service; better file timestamp awareness and full editing capability; the SauceNAO-style image search under 'system:similar files'; blurhashes; more and better system predicate parsing, and natural system predicate parsing in the normal file search input; a background database table delete system that relieves huge jobs like 'delete the PTR'; more accurate Mr. Bones and File History, and both windows now taking any search; and multiple new file formats, like HEIF and gzip and Krita, and thumbnails and full rendering for several like PSD and PDF, again in good part thanks to a user, and then most recently the Ugoira and CBZ work.

I'm truly looking forward to the new year, and I plan to keep working and putting out releases every week. I deeply appreciate the feedback and help over the years. Thank you!

next week

I have only one more week in the year before my Christmas holiday, so I'll just do some simple cleanup and little fixes.

[this-week-in-rust]

This Week in Rust 516

Hello and welcome to another issue of This Week in Rust! Rust is a programming language empowering everyone to build reliable and efficient software. This is a weekly summary of its progress and community. Want something mentioned? Tag us at @ThisWeekInRust on Twitter or @ThisWeekinRust on mastodon.social, or send us a pull request. Want to get involved? We love contributions.

This Week in Rust is openly developed on GitHub and archives can be viewed at this-week-in-rust.org. If you find any errors in this week's issue, please submit a PR.

Updates from Rust Community

Official

Announcing Rust 1.73.0

Polonius update

Project/Tooling Updates

rust-analyzer changelog #202

Announcing: pid1 Crate for Easier Rust Docker Images - FP Complete

bit_seq in Rust: A Procedural Macro for Bit Sequence Generation

tcpproxy 0.4 released

Rune 0.13

Rust on Espressif chips - September 29 2023

esp-rs quarterly planning: Q4 2023

Implementing the #[diagnostic] namespace to improve rustc error messages in complex crates

Observations/Thoughts

Safety vs Performance. A case study of C, C++ and Rust sort implementations

Raw SQL in Rust with SQLx

Thread-per-core

Edge IoT with Rust on ESP: HTTP Client

The Ultimate Data Engineering Chadstack. Running Rust inside Apache Airflow

Why Rust doesn't need a standard div_rem: An LLVM tale - CodSpeed

Making Rust supply chain attacks harder with Cackle

[video] Rust 1.73.0: Everything Revealed in 16 Minutes

Rust Walkthroughs

Let's Build A Cargo Compatible Build Tool - Part 5

How we reduced the memory usage of our Rust extension by 4x

Calling Rust from Python

Acceptance Testing embedded-hal Drivers

5 ways to instantiate Rust structs in tests

Research

Looking for Bad Apples in Rust Dependency Trees Using GraphQL and Trustfall

Miscellaneous

Rust, Open Source, Consulting - Interview with Matthias Endler

Edge IoT with Rust on ESP: Connecting WiFi

Bare-metal Rust in Android

[audio] Learn Rust in a Month of Lunches with Dave MacLeod

[video] Rust 1.73.0: Everything Revealed in 16 Minutes

[video] Rust 1.73 Release Train

[video] Why is the JavaScript ecosystem switching to Rust?

Crate of the Week

This week's crate is yarer, a library and command-line tool to evaluate mathematical expressions.

Thanks to Gianluigi Davassi for the self-suggestion!

Please submit your suggestions and votes for next week!

Call for Participation

Always wanted to contribute to open-source projects but did not know where to start? Every week we highlight some tasks from the Rust community for you to pick and get started!

Some of these tasks may also have mentors available, visit the task page for more information.

Ockam - Make ockam node delete (no args) interactive by asking the user to choose from a list of nodes to delete (tuify)

Ockam - Improve ockam enroll ----help text by adding doc comment for identity flag (clap command)

Ockam - Enroll "email: '+' character not allowed"

If you are a Rust project owner and are looking for contributors, please submit tasks here.

Updates from the Rust Project

384 pull requests were merged in the last week

formally demote tier 2 MIPS targets to tier 3

add tvOS to target_os for register_dtor

linker: remove -Zgcc-ld option

linker: remove unstable legacy CLI linker flavors

non_lifetime_binders: fix ICE in lint opaque-hidden-inferred-bound

add async_fn_in_trait lint

add a note to duplicate diagnostics

always preserve DebugInfo in DeadStoreElimination

bring back generic parameters for indices in rustc_abi and make it compile on stable

coverage: allow each coverage statement to have multiple code regions

detect missing => after match guard during parsing

diagnostics: be more careful when suggesting struct fields

don't suggest nonsense suggestions for unconstrained type vars in note_source_of_type_mismatch_constraint

dont call mir.post_mono_checks in codegen

emit feature gate warning for auto traits pre-expansion

ensure that ~const trait bounds on associated functions are in const traits or impls

extend impl's def_span to include its where clauses

fix detecting references to packed unsized fields

fix fast-path for try_eval_scalar_int

fix to register analysis passes with -Zllvm-plugins at link-time

for a single impl candidate, try to unify it with error trait ref

generalize small dominators optimization

improve the suggestion of generic_bound_failure

make FnDef 1-ZST in LLVM debuginfo

more accurately point to where default return type should go

move subtyper below reveal_all and change reveal_all

only trigger refining_impl_trait lint on reachable traits

point to full async fn for future

print normalized ty

properly export function defined in test which uses global_asm!()

remove Key impls for types that involve an AllocId

remove is global hack

remove the TypedArena::alloc_from_iter specialization

show more information when multiple impls apply

suggest pin!() instead of Pin::new() when appropriate

make subtyping explicit in MIR

do not run optimizations on trivial MIR

in smir find_crates returns Vec<Crate> instead of Option<Crate>

add Span to various smir types

miri-script: print which sysroot target we are building

miri: auto-detect no_std where possible

miri: continuation of #3054: enable spurious reads in TB

miri: do not use host floats in simd_{ceil,floor,round,trunc}

miri: ensure RET assignments do not get propagated on unwinding

miri: implement llvm.x86.aesni.* intrinsics

miri: refactor dlsym: dispatch symbols via the normal shim mechanism

miri: support getentropy on macOS as a foreign item

miri: tree Borrows: do not create new tags as 'Active'

add missing inline attributes to Duration trait impls

stabilize Option::as_(mut_)slice

reuse existing Somes in Option::(x)or

fix generic bound of str::SplitInclusive's DoubleEndedIterator impl

cargo: refactor(toml): Make manifest file layout more consitent

cargo: add new package cache lock modes

cargo: add unsupported short suggestion for --out-dir flag

cargo: crates-io: add doc comment for NewCrate struct

cargo: feat: add Edition2024

cargo: prep for automating MSRV management

cargo: set and verify all MSRVs in CI

rustdoc-search: fix bug with multi-item impl trait

rustdoc: rename issue-\d+.rs tests to have meaningful names (part 2)

rustdoc: Show enum discrimant if it is a C-like variant

rustfmt: adjust span derivation for const generics

clippy: impl_trait_in_params now supports impls and traits

clippy: into_iter_without_iter: walk up deref impl chain to find iter methods

clippy: std_instead_of_core: avoid lint inside of proc-macro

clippy: avoid invoking ignored_unit_patterns in macro definition

clippy: fix items_after_test_module for non root modules, add applicable suggestion

clippy: fix ICE in redundant_locals

clippy: fix: avoid changing drop order

clippy: improve redundant_locals help message

rust-analyzer: add config option to use rust-analyzer specific target dir

rust-analyzer: add configuration for the default action of the status bar click action in VSCode

rust-analyzer: do flyimport completions by prefix search for short paths

rust-analyzer: add assist for applying De Morgan's law to Iterator::all and Iterator::any

rust-analyzer: add backtick to surrounding and auto-closing pairs

rust-analyzer: implement tuple return type to tuple struct assist

rust-analyzer: ensure rustfmt runs when configured with ./

rust-analyzer: fix path syntax produced by the into_to_qualified_from assist

rust-analyzer: recognize custom main function as binary entrypoint for runnables

Rust Compiler Performance Triage

A quiet week, with few regressions and improvements.

Triage done by @simulacrum. Revision range: 9998f4add..84d44dd

1 Regressions, 2 Improvements, 4 Mixed; 1 of them in rollups

68 artifact comparisons made in total

Full report here

Approved RFCs

Changes to Rust follow the Rust RFC (request for comments) process. These are the RFCs that were approved for implementation this week:

No RFCs were approved this week.

Final Comment Period

Every week, the team announces the 'final comment period' for RFCs and key PRs which are reaching a decision. Express your opinions now.

RFCs

[disposition: merge] RFC: Remove implicit features in a new edition

Tracking Issues & PRs

[disposition: merge] Bump COINDUCTIVE_OVERLAP_IN_COHERENCE to deny + warn in deps

[disposition: merge] document ABI compatibility

[disposition: merge] Broaden the consequences of recursive TLS initialization

[disposition: merge] Implement BufRead for VecDeque<u8>

[disposition: merge] Tracking Issue for feature(file_set_times): FileTimes and File::set_times

[disposition: merge] impl Not, Bit{And,Or}{,Assign} for IP addresses

[disposition: close] Make RefMut Sync

[disposition: merge] Implement FusedIterator for DecodeUtf16 when the inner iterator does

[disposition: merge] Stabilize {IpAddr, Ipv6Addr}::to_canonical

[disposition: merge] rustdoc: hide #[repr(transparent)] if it isn't part of the public ABI

New and Updated RFCs

[new] Add closure-move-bindings RFC

[new] RFC: Include Future and IntoFuture in the 2024 prelude

Call for Testing

An important step for RFC implementation is for people to experiment with the implementation and give feedback, especially before stabilization. The following RFCs would benefit from user testing before moving forward:

No RFCs issued a call for testing this week.

If you are a feature implementer and would like your RFC to appear on the above list, add the new call-for-testing label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature need testing.

Upcoming Events

Rusty Events between 2023-10-11 - 2023-11-08 🦀

Virtual

2023-10-11| Virtual (Boulder, CO, US) | Boulder Elixir and Rust

Monthly Meetup

2023-10-12 - 2023-10-13 | Virtual (Brussels, BE) | EuroRust

EuroRust 2023

2023-10-12 | Virtual (Nuremberg, DE) | Rust Nuremberg

Rust Nürnberg online

2023-10-18 | Virtual (Cardiff, UK)| Rust and C++ Cardiff

Operating System Primitives (Atomics & Locks Chapter 8)

2023-10-18 | Virtual (Vancouver, BC, CA) | Vancouver Rust

Rust Study/Hack/Hang-out

2023-10-19 | Virtual (Charlottesville, NC, US) | Charlottesville Rust Meetup

Crafting Interpreters in Rust Collaboratively

2023-10-19 | Virtual (Stuttgart, DE) | Rust Community Stuttgart

Rust-Meetup

2023-10-24 | Virtual (Berlin, DE) | OpenTechSchool Berlin

Rust Hack and Learn | Mirror

2023-10-24 | Virtual (Washington, DC, US) | Rust DC

Month-end Rusting—Fun with 🍌 and 🔎!

2023-10-31 | Virtual (Dallas, TX, US) | Dallas Rust

Last Tuesday

2023-11-01 | Virtual (Indianapolis, IN, US) | Indy Rust

Indy.rs - with Social Distancing

Asia

2023-10-11 | Kuala Lumpur, MY | GoLang Malaysia

Rust Meetup Malaysia October 2023 | Event updates Telegram | Event group chat

2023-10-18 | Tokyo, JP | Tokyo Rust Meetup

Rust and the Age of High-Integrity Languages

Europe

2023-10-11 | Brussels, BE | BeCode Brussels Meetup

Rust on Web - EuroRust Conference

2023-10-12 - 2023-10-13 | Brussels, BE | EuroRust

EuroRust 2023

2023-10-12 | Brussels, BE | Rust Aarhus

Rust Aarhus - EuroRust Conference

2023-10-12 | Reading, UK | Reading Rust Workshop

Reading Rust Meetup at Browns

2023-10-17 | Helsinki, FI | Finland Rust-lang Group

Helsinki Rustaceans Meetup

2023-10-17 | Leipzig, DE | Rust - Modern Systems Programming in Leipzig

SIMD in Rust

2023-10-19 | Amsterdam, NL | Rust Developers Amsterdam Group

Rust Amsterdam Meetup @ Terraform

2023-10-19 | Wrocław, PL | Rust Wrocław

Rust Meetup #35

2023-09-19 | Virtual (Washington, DC, US) | Rust DC

Month-end Rusting—Fun with 🍌 and 🔎!

2023-10-25 | Dublin, IE | Rust Dublin

Biome, web development tooling with Rust

2023-10-26 | Augsburg, DE | Rust - Modern Systems Programming in Leipzig

Augsburg Rust Meetup #3

2023-10-26 | Delft, NL | Rust Nederland

Rust at TU Delft

2023-11-07 | Brussels, BE | Rust Aarhus

Rust Aarhus - Rust and Talk beginners edition

North America

2023-10-11 | Boulder, CO, US | Boulder Rust Meetup

First Meetup - Demo Day and Office Hours

2023-10-12 | Lehi, UT, US | Utah Rust

The Actor Model: Fearless Concurrency, Made Easy w/Chris Mena

2023-10-13 | Cambridge, MA, US | Boston Rust Meetup

Kendall Rust Lunch

2023-10-17 | San Francisco, CA, US | San Francisco Rust Study Group

Rust Hacking in Person

2023-10-18 | Brookline, MA, US | Boston Rust Meetup

Boston University Rust Lunch

2023-10-19 | Mountain View, CA, US | Mountain View Rust Meetup

Rust Meetup at Hacker Dojo

2023-10-19 | Nashville, TN, US | Music City Rust Developers

Rust Goes Where It Pleases Pt2 - Rust on the front end!

2023-10-19 | Seattle, WA, US | Seattle Rust User Group

Seattle Rust User Group - October Meetup

2023-10-25 | Austin, TX, US | Rust ATX

Rust Lunch - Fareground

2023-10-25 | Chicago, IL, US | Deep Dish Rust

Rust Happy Hour

Oceania

2023-10-17 | Christchurch, NZ | Christchurch Rust Meetup Group

Christchurch Rust meetup meeting

2023-10-26 | Brisbane, QLD, AU | Rust Brisbane

October Meetup

If you are running a Rust event please add it to the calendar to get it mentioned here. Please remember to add a link to the event too. Email the Rust Community Team for access.

Jobs

Please see the latest Who's Hiring thread on r/rust

Quote of the Week

The Rust mission -- let you write software that's fast and correct, productively -- has never been more alive. So next Rustconf, I plan to celebrate:

All the buffer overflows I didn't create, thanks to Rust

All the unit tests I didn't have to write, thanks to its type system

All the null checks I didn't have to write thanks to Option and Result

All the JS I didn't have to write thanks to WebAssembly

All the impossible states I didn't have to assert "This can never actually happen"

All the JSON field keys I didn't have to manually type in thanks to Serde

All the missing SQL column bugs I caught at compiletime thanks to Diesel

All the race conditions I never had to worry about thanks to the borrow checker

All the connections I can accept concurrently thanks to Tokio

All the formatting comments I didn't have to leave on PRs thanks to Rustfmt

All the performance footguns I didn't create thanks to Clippy

– Adam Chalmers in their RustConf 2023 recap

Thanks to robin for the suggestion!

Please submit quotes and vote for next week!

This Week in Rust is edited by: nellshamrell, llogiq, cdmistman, ericseppanen, extrawurst, andrewpollack, U007D, kolharsam, joelmarcey, mariannegoldin, bennyvasquez.

Email list hosting is sponsored by The Rust Foundation

Discuss on r/rust

[biglisbonnews]

Energy dashboard missing some bars Recently I acquired a sensor for the electricity meter. The sensor page is in PT, but is a tasmota that was adjusted to the meters used in Portugal. It is connected through MQTT and I have the values in Home Assistant and the database: However, the energy dashboard has a strange behaviour: There are mentions of similar issues, but all appear to fix themselves after one update or by changing the browser. HomeAssistant is being deployed in an RPI4 with the following docker-compose: version: '3' services: homeassistant: container_name: homeassistant image: "ghcr.io/home-assistant/home-assistant:stable" restart: unless-stopped environment: - TZ=Europe/Lisbon volumes: - ./config/:/config - /etc/localtime:/etc/localtime:ro privileged: true network_mode: host depends_on: - mosquitto - mariadb - influxdb mosquitto: image: eclipse-mosquitto container_name: mosquitto volumes: - ./mosquitto:/mosquitto restart: unless-stopped network_mode: host mariadb: container_name: mariadb image: mariadb restart: unless-stopped ports: - "13306:3306/tcp" # So we can access the WebUI environment: - TZ=Europe/Lisbon - MYSQL_ROOT_PASSWORD=${MYSQL_ROOT_PASSWORD} - MYSQL_DATABASE=${MYSQL_HA_DATABASE} - MYSQL_USER=${MYSQL_HA_USER} - MYSQL_PASSWORD=${MYSQL_HA_PASSWORD} volumes: - ./mariadb/data:/var/lib/mysql - ./mariadb/config/:/etc/mysql/conf.d influxdb: container_name: influxdb image: influxdb restart: unless-stopped ports: - "8086:8086/tcp" # So we can access the WebUI environment: - TZ=Europe/Lisbon - DOCKER_INFLUXDB_INIT_MODE=setup - DOCKER_INFLUXDB_INIT_USERNAME=${INFLUXDB_USER} - DOCKER_INFLUXDB_INIT_PASSWORD=${INFLUXDB_PASSWORD} - DOCKER_INFLUXDB_INIT_ORG=${INFLUXDB_ORG} - DOCKER_INFLUXDB_INIT_BUCKET=${INFLUXDB_BUCKET} volumes: - ./influxdb/data:/var/lib/influxdb2 - ./influxdb/config/:/etc/influxdb2 ulimits: nofile: soft: 32768 hard: 32768 And the configuration file for home assistant is the following: # Loads default set of integrations. Do not remove. default_config: # Text to speech tts: - platform: google_translate automation: !include automations.yaml script: !include scripts.yaml scene: !include scenes.yaml http: use_x_forwarded_for: true trusted_proxies: - 127.0.0.1 - ::1 - 192.168.1.0/24 recorder: db_url: !secret mariadb purge_keep_days: 10 # default history: influxdb: api_version: 2 ssl: false host: 127.0.0.1 port: 8086 token: !secret influxdb_token organization: !secret influx_org bucket: homeassistant tags: source: HomeAssistant tags_attributes: - friendly_name default_measurement: units ignore_attributes: - icon exclude: # Customise to fit your needs entities: - zone.home domains: - persistent_notification - person Since the sensor values are in the database, I don’t think the issue is in the deployment. I also have no errors in the logs, nor issues in the statistics dev menu. Any idea? 2 posts - 2 participants Read full topic https://community.home-assistant.io/t/energy-dashboard-missing-some-bars/601366

[draegerit]

Home Assistant auf Raspberry Pi installieren

In diesem Beitrag erfährst du, wie man das System Home Assistant auf einen Raspberry Pi installiert.

Ich verwende einen Raspberry Pi 3B+ welcher mit 1.4 GHz und 1 GB RAM mit doch recht ausreichend Kapazitäten daher kommt.

Benötigte Ressourcen

In meinem Fall möchte ich zunächst nur Home Assistant auf den Pi installieren, d.h. ich benötigte lediglich: - einen Raspberry Pi 3B+ oder besser Pi 4, - eine SD-Karte mit 32 GB Speicherplatz, - ein Micor-USB Netzteil mit min. 2.5 A Leistung, - ggf. ein Netzwerkkabel Das Netzwerkkabel benötigt du nur, wenn du kein lokales WLAN hast und du diesen über einen Hub / Switch anschließen musst.

Raspberry OS

Für diesen Beitrag verwende ich mein bestehendes System mit einem Raspberry OS, welches ich zunächst mit dem Befehl "sudo apt-get upgrade -y" aktualisiere. Wie du ein Raspberry OS installierst, habe ich dir bereits im Beitrag Raspberry PI : Installation ausführlich erläutert. Damit ich die Installation durchführen konnte, musste ich auf die aktuelle Version des Raspbian OS upgraden. Hier habe ich per Imager ein neues OS auf die SD-Karte geschrieben.

Installieren von Home Assistant

Die Installation von Home Assistant auf einen Raspberry Pi ist auf der englischen Seite https://www.home-assistant.io/installation/raspberrypi sehr ausführlich beschrieben. Hier möchte ich nun gerne an diese Anleitung anknüpfen und dir das Ganze einmal auf Deutsch erläutern. Installieren von Docker Das System Home Assistant läuft in einem Docker Container. Jedoch ist Docker nicht unbedingt vorinstalliert und daher müssen wir dieses zunächst tun. Zur Installation und konfiguration können wir entweder die Befehle auf dem Terminal eingeben oder wir nutzen ein Shell Skript von Docker, welches das ganze für uns erledigt. curl -fsSL https://get.Docker.com -o get-Docker.sh sudo sh get-Docker.sh In meinem Fall habe ich heute (06.05.2023) nachfolgendes Paket installiert bzw. installieren lassen. Client: Docker Engine - Community Version: 23.0.5 API version: 1.42 Go version: go1.19.8 Git commit: bc4487a Built: Wed Apr 26 16:17:05 2023 OS/Arch: linux/arm Context: default Server: Docker Engine - Community Engine: Version: 23.0.5 API version: 1.42 (minimum version 1.12) Go version: go1.19.8 Git commit: 94d3ad6 Built: Wed Apr 26 16:17:05 2023 OS/Arch: linux/arm Experimental: false containerd: Version: 1.6.21 GitCommit: 3dce8eb055cbb6872793272b4f20ed16117344f8 runc: Version: 1.1.7 GitCommit: v1.1.7-0-g860f061 docker-init: Version: 0.19.0 GitCommit: de40ad0 Benutzerberechtigungen setzen Da man unter Linux nicht direkt mit dem Benutzer root arbeiten soll und ich dieses auch mache, muss ich den Benutzer pi noch in die Gruppe der Docker Benutzer hinzufügen. sudo usermod -aG docker $USER newgrp docker Testen der Docker Installation Bevor wir jetzt mit der Installation von Home Assistant starten, testen wir zunächst, ob die Docker Installation erfolgreich war. Dazu laden wir den Container "Hello-World" vom Docker Repository https://hub.docker.com/_/hello-world. Du findest auf der Seite oben rechts auch den Befehl um dir den Container herunterzuladen.

Hello-World Container im Docker Repository Wenn der Container mit "docker pull hello-world" heruntergeladen wurde, können wir danach mit "docker run hello-world" diesen ausführen. Wenn das ganze erfolgreich war, dann sollten wir die nachfolgende Ausgabe sehen. pi@raspberrypi:~ $ docker pull hello-world Using default tag: latest latest: Pulling from library/hello-world c4018b8bf438: Pull complete Digest: sha256:9eabfcf6034695c4f6208296be9090b0a3487e20fb6a5cb056525242621cf73d Status: Downloaded newer image for hello-world:latest docker.io/library/hello-world:latest pi@raspberrypi:~ $ docker run hello-world Hello from Docker! This message shows that your installation appears to be working correctly. To generate this message, Docker took the following steps: 1. The Docker client contacted the Docker daemon. 2. The Docker daemon pulled the "hello-world" image from the Docker Hub. (arm32v7) 3. The Docker daemon created a new container from that image which runs the executable that produces the output you are currently reading. 4. The Docker daemon streamed that output to the Docker client, which sent it to your terminal. To try something more ambitious, you can run an Ubuntu container with: $ docker run -it ubuntu bash Share images, automate workflows, and more with a free Docker ID: https://hub.docker.com/ For more examples and ideas, visit: https://docs.docker.com/get-started/ pi@raspberrypi:~ $

Container Home Assistant aus dem Docker Repository laden

Nachdem Docker installiert und erfolgreich getestet wurde, können mit der Installation von Home Assistant fortfahren.

Home-Assistant Container im Docker Repository Zuerst laden wir uns den Container vom Docker Repository mit "docker pull homeassistant/home-assistant" herunter.

Starten von Home Assistant

Wenn der Container geladen wurde, dann können wir mit dem nachfolgenden Befehl, den Container starten. docker run -d --name homeassistant --privileged --restart=unless-stopped -e TZ=MY_TIME_ZONE -v /PATH_TO_YOUR_CONFIG:/config --network=host ghcr.io/home-assistant/home-assistant:stable Auf der Konsole solltest du nun folgende Ausgabe sehen: Wenn wir nun im Browser die IP-Adresse des Raspberry Pi gefolgt vom Port 8123 eingeben, dann sollten wir das Fenster für die Einrichtung eines Benutzers für Home Assistant sehen.

Wenn der Benutzer angelegt wurde, dann müssen noch ein paar Einstellungen getroffen werden. Im dritten Dialog, wo man gebeten wird Statistiken zu versenden, hake ich nichts an!

Ein Gerät hinzufügen

Als Erstes möchte ich dem Dashboard ein neues Gerät hinzufügen. Derzeit habe ich einige Shellys im Haus (und auch draußen) verbaut. Zum Beispiel läuft mein 3D Drucker über einen Shelly Plus Plug S welcher den Stromverbrauch misst. Diesen Shelly Plug S möchte ich als erstes Einrichten und klicke auf die Einstellungen (1) unten links. Danach wähle ich den Menüpunkt Geräte & Dienste (2). Es werden jetzt Geräte aufgelistet, welche im Netzwerk gefunden wurden, aus dieser Liste wähle ich die Schaltfläche Konfigurieren (3) aus. Den nächsten Dialog bestätigen wir einfach mit Absenden (4). Zum Schluss muss dieses Gerät noch einem Raum zugeordnet werden, per Default sind bereits drei Räume konfiguriert. Du kannst aber auch recht einfach einen neuen Raum hinzufügen, was ich in meinem Fall getan habe und bestätige die Auswahl Keller (5) mit dem Link Fertig (6). Wenn das abgeschlossen ist, dann findest du den Shelly im Dashboard mit seinen Eigenschaften.

Was besonders gut funktioniert ist, die Synchronisation zwischen dem Dashboard und dem Gerät. Im nachfolgenden Video habe ich das Dashboard von Home Assistant und der Shelly Cloud geöffnet und aktiviere / deaktiviere den Shelly bzw. den angeschlossenen Verbraucher. Read the full article