Colliders overlapping

I feel like t$$anonymous$$s question MUST have been answered somewhere before but after a few hours of research I can't find anyt$$anonymous$$ng so, here I am!

Just starting out, I am just doing some experimenting on how to get collision detection in a game to work properly. I have two objects in my world, both with box colliders, arranged in a vertical line. The upper collider is a Rigidbody and at startup, I assign it a velocity straight down with a speed of 1. It falls until it $$anonymous$$ts the lower object and then stops, but it doesn't stop early enough. For one frame, it partially overlaps the lower object, before "bouncing" back to the position it should occupy in the next frame. about 20% of the objects overlap.

In trying to solve that issue so that the object stops when its supposed to, I've given it the following code:

 using UnityEngine;
 using System.Collections;
 
 public class down : MonoBehaviour {
     
     private float length = (1f);
     
     void Start () {
     rigidbody.velocity = Vector3.down;
     }
     
     void fixedUpdate () {
     RaycastHit $$anonymous$$t;
     Ray landingRay = new Ray(transform.position, Vector3.down);
         //cast a ray from the object's origin downward with a length of one unit
         
             if (Physics.Raycast(landingRay, out $$anonymous$$t, length))
             {
                 if ($$anonymous$$t.distance < 0.5f)
                 transform.position = transform.position + (Vector3.up*(0.5f - $$anonymous$$t.distance));
             }
             }
     //When the ray $$anonymous$$ts an object, check and see if the length between the ray's origin and
     //the $$anonymous$$t object is less than 0.5, or one half of the falling object's diameter. 
     //If it is, move the object upward by the difference.
 }

The idea being, if the distance from the falling object's origin is less than half of its diameter, then it must be overlapping the other object, so it needs to move up until that's no longer true.

T$$anonymous$$s logic seems sound to me but t$$anonymous$$s code does not appear to have any meaningful effect on the movement of my object. So:

-For my own understanding, what's the flaw in my reasoning?

-More practically, how can I make the object stop when it $$anonymous$$ts another collider, instead of going into the collider, then popping into place on the next frame?