Here's a simple command to get human-readable sizes of files and folders inside of the current directory. (I've tested it on macOS' Terminal and Linux.)
du -sh -- * # 124M backups # 523M downloads # 1.8G recordings-hijack # 673M recordings-obs # 392K recordings-zoom # 403M settings
Note that you may have to
sudo if you're trying to get sizes for files that require
"The following command runs an
ubuntu container, attaches interactively to your local command-line session, and runs
/bin/bash," reads the official Docker starter guide.
docker run -it ubuntu /bin/bash
docker run -it ubuntu /bin/bash # List files inside of the Docker container root@642064598df6:/ ls # bin dev home lib32 libx32 mnt proc run srv tmp var # boot etc lib lib64 media opt root sbin sys usr # Print the current directory root@642064598df6:/ pwd # / # Exit the instance root@642064598df6:/ exit # exit
Here's a summary from Docker's docs.
When you run this command, the following happens (assuming you are using the default registry configuration):
docker pull ubuntu).
docker container createcommand manually).
/bin/bash. Because the container is running interactively and attached to your terminal (due to the
-tflags), you can provide input using your keyboard while the output is logged to your terminal.
When you type
exit to terminate the
/bin/bash command, the container stops but is not removed. You can start it again or remove it.
If you don't want your container to persist after you
exit, you should use the
docker run -it --rm ubuntu /bin/bash
In DigitalOcean, running the
do-release-upgrade command was returning the following message.
Checking for a new Ubuntu release Please install all available updates for your release before upgrading.
sudo apt-get update
sudo apt-get upgrade -y
sudo apt-get dist-upgrade
shutdown -r now
You could stop here if all you want is to install available updates. Read the warning below to make sure you don't break your live applications and whether this is the best approach you can take.
WARNING: Please read this article by DigitalOcean on the potential pitfalls of upgrading an existing installation with your applications running on it. Instead of upgrading in-place, the recommended approach is to migrate your applications by creating a new, fresh instance with Ubuntu 20.04 LTS instead of upgrading an existing one. (Run at your own risk!)