docker-base | These base images | Continuous Deployment library

I have a normal monolith app running on Heroku. I would like to use an SQS queue to process some background jobs.

Monolith -> posts to SQS -> SQS holds event & calls -> Monolith -> Confirms processing and deletes event from SQS

I already have an S3 bucket I have configured via the AWS CDK, now I'm trying to figure out to configure an SQS queue which I can also call from the outside (via access_token/key authentication):

Using psql with COPY FROM STDIN works fine when executed via -c (inline command) but the same thing fails if -f (script file) is used. I've created a Docker-based test to demonstrate below; tested on MacOS w/ zsh and Debian w/ bash.

I was unable to find any relevant documentation on why this would be but I imagine it has to do with psql's special \copy functionality. Can someone help illuminate me?

I am building a Dev Docker environment and I have to set up an Oracle 19c database.

I have been successful... but not at 100%.

Everything is running correctly, I can create a tablespace, a user/schema, create a table, insert data, access via NodeJs the data too until I restart the container.

In all the tutorials, it is shown to mount a volume pointing to /opt/oracle/oradata

I'm trying to parametrize a Jenkins pipeline with a File type parameter to be used on a docker based agent.

Added a_file parameter, the environment variable is available while executing, but not the file.

Is there any specific steps or way to use file parameters on the Docker-based agent?

An excerpt of the pipeline:

Are there any special reasons why Cygwin Clang is so outdated (see here), version 8, while already version 13 exists?

For example Ubuntu (apt), MSYS2, MSVC all have version 12.

Also does anyone know (any links?) if there is any very simple way (like docker-based) to build recent Clang for Cygwin? Maybe Clang has no support for Cygwin anymore, that's why Cygwin has outdated version?

1. I installed Docker and Docker Compose
2. I downloaded the latest release Docker-based Drupal stack (there are php, mariadb, apache images etc.) and put it in the my project folder /var/www/html/mydrupaldocker
3. Next, I made the settings in the .env and docker-compose.yml files and running the containers with the command:
   docker-compose up -d
4. After running images from this folder, as well as adding the unzip drupal 9 folder to the my project folder, I will start installing drupal 9 in the browser.
   

And I have questions on two possible situations:

Situation №1:

I made mistakes in the file docker-compose.yml I have the commented code which is responsible for the few images. Accordingly, the containers were not started. And I want to place the project in another place of the computer (not critical, but it is desirable)

I can do:
docker-compose stop
docker-compose rm

Fix everything that I need. And run again:

docker-compose up -d

Is it right to do so? Or do I need something otherwise?

Situation №2:

Everything is set up well, running all the necessary containers, installed the Drupal 9 site in the container. And then I created a sub theme, added content, wrote code in php, js, css files, etc.

How do I commit the changes now? What commands do you need to write in the terminal? For example, in technology such as git, this is done with the commands:
git add.
git commit -m "first"

How is it done in Docker? Perhaps there will be a situation when I need to roll back the container to the version below.

I need a way to copy my manifest and all related blobs/etc from a private registry to a public registry, where the images were never pushed to the public registry before.

I am successfully creating a multi-arch manifest via buildah. Note that while the image is built with buildah, I would be satisfied with a docker-based approach for copying the final result between registries. Here is the output from buildah inspect:

I'm trying to create a Windows Docker container using Kaniko/Gitlab.
Here is the Error I see: