procps | Mirror of procps CVS repository | Genomics library

I need to deploy a Jenkins container with https enabled using docker-compose without using a reverse-proxy like Nginx, how can I accomplish this?

I have read this post, this blog post, and this blog post all of witch require me to deploy the .war file with java parameters like --httpPort and --httpsPort.

Where do I put these options in my docker-compose file? I also have a Dockerfile where I run some commands post install, is it possible to put these options there?

Here is my current docker-compose file, which works. Note I am not trying to adjust the http or https ports in this file:

I have some issue when I try to manage docker-compose and dockerfile together. I researched and I know that is possible to use docker-compose without a dockerfile, but I think for me is better to use Dockerfile too because I want an environment to be easy to be modified. The problem is that I want to have a container with postgres, which is a dependent component to another container, container named api which is used to run the application. This container contains Java 17 and Maven 3 and take using docker-compose, image from Dockerfile. The problem is: while I use Dockerfile, everything is fine, but actually when I use docker-compose, I got this error: 2021-12-08T08:36:37.221247254Z /usr/local/bin/mvn-entrypoint.sh: line 50: exec: mvn test: not found

Configuration files are:

• Dockerfile

I'm buildinga a docker image using a Dockerfile to build it. I have put ARG DEBIAN_FRONTEND=noninteractive in the beginning of the Dockerfile to avoid debconf warnings while building.

The warnings does not show up when using apt-get install inside the Dockerfile. However when executing a sh script (install_dependencies.sh) from the Dockerfile that contains apt-get install commands, the warnings show up again. I also tried to set DEBIAN_FRONTEND=noninteractive inside the sh script itself.

I can solve this by adding echo 'debconf debconf/frontend select Noninteractive' | sudo debconf-set-selections in the sh script before the apt-get install commands but I would want to avoid that, since any fail in the script would leave debconf select to Noninteractive.

Dockerfile:

Created a small .Net 5.0 application in Visual Studio 2019 and added docker-compose container orchestration support to it using linux containers. I set the docker-compose project as the default startup application in Visual Studio, and everything was going great for two days until I decided to alter my configuration so my container would have a stable port number instead of it randomly changing.

I'm not sure what I did but but Visual Studio doesn't attach to the container anymore, and the browser window that normally opens when the container starts no longer does. The container is running but the app doesn't respond to the new port number I'm trying or the older port number either.

The code builds fine in VS, the Dockerfile builds successfully, and the docker-compose up command runs in Visual Studio just fine.

I have portainer running in my docker-compose file and I can see that the container is running but it is not producing any logs. I logged into to my running container using portainer and installed the procps package like so: apt-get update; apt-get -y install procps. When I run ps I see that my app is not actually running.

I've had some issues at implementing built-in jena-fuseki reasoner, I could make it work but it would not prevent me from adding incorrect triples. So I wanted to add Openllet reasoner to my jena-fuseki server.

But I can't figure how to add openllet jar to my Docker image and make it work, I've run into many java dependances issues. To add context, my docker-compose looks like that :

I have the following Dockerfile with a bit of customization for Nginx server. I build the image with docker build -t nginx-custom:1.21.1 . command finished without errors. But when I want to create a container from this image with docker run -it -d nginx-custom:1.21.1 /bin/bash command also not appears any errors. But when I enter to container with docker exec command and check running processes with ps -ef the result contains only the bash process.

I've got a Python application that polls a queue for new data, and inserts it into a TimescaleDB database (TimescaleDB is an extension for PostgreSQL). This application must stay running at all times.

The problem is, the Python program may fail from time to time, and I expect Docker Swarm to restart the container. However, the containers keep running even after failure. Why aren't my containers failing and then being restarted by Docker Swarm?

The Python app looks something like this:

I am encountering an error when I am building a Cloud Run container from a particular directory in a GCP project. This particular directory has always built correctly in the past, and no changes were made to it since the last successful build.

Recently, however, I wanted to fire up a pipeline for this directory, so I added a few pound signs to the code (so the Cloud Build trigger could start building the Run container - additionally, the addition of these pound signs should not affect anything in the code). In the process, this error showed up:

I have a program that builds servers automatically whenever we want stakeholders to test a new feature.

Currently I have the following setup:

1. Container 1 - all (contains nodejs, php and other dependencies)
2. Container 2 - db (contains the mysql database)

I'm aware that container 1 should be split but this will involve more unnecessary complexity to this stage of development.

Whenever a new feature is completed and ready to be deployed to a stage server we run: yarn run create:server --branchName=new-feature. This will create all of the configuration necessary to bring up our newly created server.

My problem is that whenever I run the command above I need to create a database in db container from all container: