docker-machine | Docker Machine maintained by GitLab for fixing critical bugs | Continuous Deployment library

SOLVED

The solution here is not to ssh into the VM, and instead to change to the VM context with:

Homebrew does not support your os version, so you'll need to use the he install_ddev.sh technique. See the script installation technique at https://ddev.readthedocs.io/en/stable/

I imagine you'll also find that docker desktop doesn't support your os version though.

To install via sh script. Can run below script :

curl -LO https://raw.githubusercontent.com/drud/ddev/master/scripts/install_ddev.sh && bash install_ddev.sh

Followup: @aviboy2006 posted a complete tutorial on how to do ddev/docker on an old Mac: https://www.internetkatta.com/installation-of-ddev-docker-and-virtual-box-on-mac-os-10126

I've never used docker toolbox on the mac, but on Windows with Docker Toolbox, only your home directory is shared by default. It looks like you have the project in /Library/WebServer/Documents, which is not your home directory. I recommend that you either put the project in your home directory or research how to share /Library/Webserver/Documents with Docker Toolbox. I think you'll likely find some answers about this here: https://www.google.com/search?q=docker+toolbox+shared+drives+macos&sxsrf=ALeKk00SOQVEtAU9hFcHPoxV75aJoMcWgQ%3A1621959319429&ei=lyKtYL_OGcqttQaEnI2ABg&oq=docker+toolbox+shared+drives+macos&gs_lcp=Cgdnd3Mtd2l6EAMyBQgAEM0COgcIIxCwAxAnOgcIABBHELADOgYIABAWEB46CAghEBYQHRAeOgcIIRAKEKABOgUIIRCrAlCoc1jsgQFgh4QBaAFwAngAgAHrAogB9AeSAQcxLjUuMC4xmAEAoAEBqgEHZ3dzLXdpesgBCcABAQ&sclient=gws-wiz&ved=0ahUKEwj_9cuoneXwAhXKVs0KHQROA2AQ4dUDCBE&uact=5

Please note that Docker Toolbox on Mac has never been tried by anybody else to my knowledge. Also note that you can download ancient versions of Docker Desktop from https://docs.docker.com/docker-for-mac/release-notes/

adding --rm to a docker container run command should remove my container as I exit from it.

This is a misconception. The --rm flag tells Docker to remove the container when it stops.

I see you passed no extra flags to your docker container run command, so I'll assume you attach to your container after starting it. Detaching from a container does not stop it automatically, unless the container is started with the -i flag, which should automatically attach stdin/stdout to the container with that run command.

To remove a container that was started with --rm flag, you cam simply docker stop it and it'll be gone.

I'm a little unsure what you're asking, but it seems like you may need to expose your ports. When running something in Docker, it runs in its own little box unconnected to the outside world - the rest of your machine. If you want to connect ports - say to access a web server running inside a Docker container, you need to use the -p or --publish option when running your Docker container. There are similar commands for mounting drives and such.

Here's an example from the database I run locally in Docker:

It is clear that your EC2 instance has disk usage issue (disk gets full). You successfully increased the volume size (as shown in lsblk output) but you also need to extend the file system, as described here.

Essentially, you should run sudo growpart /dev/xvda 1 and sudo resize2fs /dev/xvda1. Use df -h again to verify.

In order to optimize performance, you should consider:

• Using a dedicated volume for your workload (i.e. mount a new, larger EBS volume on /mnt/data and configure your application to use this path for data storage)
• Resize this volume and/or change type (i.e. use provisioned IOPS SSD)

Scrapy also supports S3 for storage.

You can configure scrapy logging to use a specific log file (--logfile FILE which you can later delete) or disabled it altogether (--nolog, not recommended).

You might be using incorrect certificates to sign the transaction. Your certificates and the artifacts are not matching. My suggestion is to delete the docker volume and regenerate the certs and artifacts (genesis block and channel transaction)

This is difficult because you cannot guarantee a clean shutdown. Machines freeze and crash sometimes. You're better off cleaning up at startup.

You can create another systemd-service to clean up and place a dependency on it from the service that starts your containers.

Or, it may be better to simply put a 'restart always' policy on your containers and docker will just restart them for you automatically when the system reboots.

A Docker container generally only runs a single process. You don't need to "start a service" or "restart a service"; generally the server process itself is the main container process, and if you need to restart the service, you restart the entire container. Often "service"-type commands are missing some key piece of infrastructure in a Docker context and just won't work.

In your Dockerfile, you can just make the main command be to launch Nginx as a foreground process