This turns out to be my command line error. The arguments of docker run need to follow the right order.
i.e.
This will ignore the port mapping:
docker run 09dad155f3cc -d -p 8080:8080/tcpand this will work as expected:
docker run -p 8080:8080/tcp 09dad155f3cc -dWhen building a Dockerfile from my MacBook:
> docker build .Sending build context to Docker daemon 123kBStep 1/8 : FROM debian:jessiejessie: Pulling from library/debianno matching manifest for linux/arm64/v8 in the manifest list entries
A quick search of the error “no matching manifest for linux/arm64/v8 in the manifest list entries” indicates it has to do with Apple M1 Chip.
Workaround
Pull the image with the platform specified:
> docker pull — platform linux/amd64 debian:jessieThen run build again:
> docker build .Below is my ‘quick fix’ (bandaid) solution to the following errors/exceptions.
The errors
Error: Execution of '/usr/bin/gem install --no-rdoc --no-ri cowsay' returned 1: ERROR: While executing gem ... (OptionParser::InvalidOption)invalid option: --no-rdocDid you mean? no-force
A reference article https://github.com/puphpet/puphpet/issues/2838
The ‘quick fix’
W.r.t. the reference article, I searched for the file ‘gem.rb’. Since ‘locate’ was not installed in the OS, I used the ‘find’ command to look for the file:
> find / -name 'gem.rb'
/usr/lib/ruby/vendor_ruby/puppet/provider/package/gem.rbIn the gem.rb file, I found the line throwing the exception and made the following modification:
#command << "--no-rdoc" << "--no-ri" << resource[:name]
command << "--no-document" << resource[:name]
I have just started using Azure cloud. As a frugal engineer, I will make full use of the 30 days free tier.
As I added more VMs to my free account, it finally hit the limit. On the Virtual Machines page, I could not find a button to downsize the ones I already created (even if I power the VM down). So I started deleting them to free up the limit.
But the following error persisted, even after I deleted every VM/refreshed the page:
“X vCPUs are needed for this configuration, but only 0 vCPUs (of 4) remain in your subscription.”
Eventually it turns out that there’s a need to click on the ‘Refresh quota’ link (a Blue hyperlink below the error), so it will get rid of the error.
