You need to set a volume in your docker-compose file that points to where your sqlite file is located,docker-compose. _ version: "3"services: app: restart: on-failure build: . container_name: myapp volumes: - ./code:/app ports: - "5000:5000" dockerfileFROM python:3.6 ADD ./code /app WORKDIR /app RUN pip install -r requirements.txt CMD python run.py With the volume set, the files of the code folder will be mirrored into the app folder inside the container. Maybe that solves your problem.Edit https://github.com/LuisMSoares/sqlite-docker-compose

In a Docker-based infrastructure, managing a single server, or 2 servers is a simple task. But there are scenarios where you have hundreds or even thousands of servers, and the decisions that need to be made are:Move server A container to server BEliminate a container (and need to find out which server it is)Go up a set of containers that need to talk between themselves and so need to be on a logical network, but not necessarily on the same server.There are cases where these decisions need to happen on account of a crashed host, not responding, is dead or simply failed.All these dynamics are complex and take time to manage. Docker doesn't solve that, but he solves everything else we already know. Thus orchestrators emerge as mechanisms that manage the full complexity of delivering large-scale management. They deliver the ability to manage many hosts from a unified perspective of processing unit, and this completely changes the way we can scale applications, isolate applications, and manage idle hardware.

The Answer in the case presented is in /home/DockerFolder.

Every image is defined by [owner]/[repository]:[tag], the images of the library (official images) have no owner.When we delete the tag, we automatically tell the docker that we should pick up the "latest". So you need to go in the docker hub, find the appropriate image and look at your tags. You will find the tags available like this.Then just hit your docker-compose by placing the tag that matches the version you want.The only point of attention is that not necessarily the version you want can be available in the docker hub. That happens.

The error permission denied probably means your file docker-entrypoint.sh is without read and/or run permissions.The three basic permissions for files are:(R) Read: Ensure permission to read the content of a file(W) Writing: Allows you to change the content of a file(X) Execution: Allows execution of a file if these are programs (files that are not programs ideally should not have execution permissions)Verify your permissions docker-entrypoint.sh and ensure read and run permissions:$ ls -l docker-entrypoint.sh -r-xr-xr-x 1 user user 25 set 17 10:33 docker-entrypoint.sh Use chmod For https://www.vivaolinux.com.br/dica/Como-dar-Permissao-de-Execucao-a-Arquivo-script-ou-binario-no-GNULinux-Abordagem-Pratica as required:chmod +r docker-entrypoint.sh for reading permissionschmod +x docker-entrypoint.sh for execution permissions

Use the name of your docker container as host in case by what I understand you named your container with "mysql-docker", if you have doubts about the name run "docker ps -a" and check the container nameconst mysql = require('mysql'); const connection = mysql.createConnection({ host: 'mysql-docker', port: 3306, user: 'root', password: 'password', });

I managed to fix it.Solution:The daemon.json file should also be configured on workers and not just in manager.I also changed the name of the localhost image:5000 to 10.0.0.77:5000 (ip of the manager)/etc/docker/daemon. json{ "insecure-registries":[ "10.0.0.77:5000" ] } In summaryIn the workers, I created the daemon file. json with insecure-registries and restarted the dockerIn the manager, I ran the registry as a container even.docker run -d -p 5000:5000 registry:2 I created a new image tag (I didn't use latest because I want to know exactly what version is being executed by Portainer) docker tag integration-toa:14 10.0.0.77:5000/integration to:14I sent via push to the local registry the image:docker push 10.0.0.77:5000/integracao-toa:14 I performed the service of my application and used the "contraint" to be published only on the workers (I added a label called group=group01 on the two workers, so I can control by the manager on which machines my application will deploy)docker service create --name integracao-toa --constraint node.labels.group==group01 --replicas 2 -p 3000:80 10.0.0.77:5000/integracao-toa:14 and again, I ran with the specific tag of version 14, instead of the latest, so I can more consistently view the version being executed each node

By using the configuration https://docs.docker.com/compose/compose-file/#links , you are specifying a service:alias that allows the said container to be accessible using the service name and/or alias defined.For example. When setting:php-fpm: links: - mysql - mysql:database Your container php-fpm can communicate with your database both by hostname mysql how much by database.In your case, you must exchange your DB_HOST, 127.0.0.1 means that php-fpm is trying to connect in itself, and not in the database container. The right thing is to stay like this:DB_CONNECTION=mysql DB_HOST=mysql DB_PORT=3306 ... Important to note that the configuration links is depreciated, and can be removed from Docker at any time.Take a look at the configuration https://docs.docker.com/compose/networking/ to understand recommended way to configure the container network.

You have to work with volumes to save the data out of the container, when upgrading only changes the container image, but the data is the same

I'm sorry, but I didn't understand your problem. In the log presented there was no failure, otherwise it only succeeded. The WARNs presented were by the outdated npm version that can be updated with the following command: npm@latest -g

Following https://docs.docker.com/docker-hub/repos/#pushing-a-repository-image-to-docker-hub :To push a repository to the Docker Hub, you need to name your local image using your Docker Hub username, and the repository name that you created in the previous step [...]You need to create a tag to use the image before climbing:At the time of build: $ docker build -t <hub-user>/<repo-name>[:<tag>] orImage already created: $ docker tag <existing-image> <hub-user>/<repo-name>[:<tag>]And then to go up to the remote repository:$ docker push <hub-user>/<repo-name>:<tag> Where:hub-user: Your user in DockerHubrepo-name: the remote repository name in DockerHubexisting-image: image already builttag: Tag for the image (e.g v1.0)And in your case, you would do so, for example:Add to Tag in your image: $ docker tag projetofinal2_web:latest <seu_usuario_dockerhub>/<seu_repo_dockerhub>:v1.0And then do it push:$ docker push <seu_usuario-dockerhub>/<seu_repo_dockerhub:v0.1

If you want your container "see" some directory of your machine, need to mount a volume, where it will map a local directory inside the container.Ex. https://hub.docker.com/_/redmine/ $ docker run -d --name some-redmine -v /my/own/datadir:/usr/src/redmine/files --link some-postgres:postgres redmine Where,-v /my/own/datadir:/usr/src/redmine/files will map the my/own/datadir of your machine in /usr/src/redmine/files inside the container.

I decided as follows:Docker!FROM centos:7 This bit is exactly as per the documentation and can be stuck existing Dockerfiles without issue ENV container docker RUN (cd /lib/systemd/system/sysinit.target.wants/; for i in ; do [ $i == systemd-tmpfiles-setup.service ] || rm -f $i; done); rm -f /lib/systemd/system/multi-user.target.wants/; rm -f /etc/systemd/system/.wants/; rm -f /lib/systemd/system/local-fs.target.wants/; rm -f /lib/systemd/system/sockets.target.wants/udev; rm -f /lib/systemd/system/sockets.target.wants/initctl; rm -f /lib/systemd/system/basic.target.wants/; rm -f /lib/systemd/system/anaconda.target.wants/*; VOLUME [ "/sys/fs/cgroup" ] RUN yum -y install epel-release; RUN yum -y install python-pip python-devel gcc nginx; RUN pip install virtualenv WORKDIR /usr/share/myproject EXPOSE 80 COPY requirements.txt . RUN mkdir /usr/share/myproject/app COPY myproject.py /usr/share/myproject/app RUN cd app && virtualenv myprojectenv && source myprojectenv/bin/activate && pip install --no-cache-dir -r $PWD/../requirements.txt COPY myproject.service /etc/systemd/system/myproject.service COPY wsgi.py /usr/share/myproject/app/wsgi.py COPY index.html /usr/share/myproject/app/index.html COPY nginx.conf /etc/nginx/nginx.conf RUN systemctl enable myproject RUN systemctl enable nginx CMD ["/usr/sbin/init"] myproject. ♪from flask import Flask application = Flask(name) @application.route("/") def hello(): return "<h1 style='color:red'>Hello There!</h1>" @application.route("/azul") def helloa(): return "<h1 style='color:blue'>Hello There!</h1>" if name == "main": application.run(host='0.0.0.0') myproject. service[Unit] Description=Gunicorn instance to serve myproject After=network.target [Service] User=root Group=nginx WorkingDirectory=/usr/share/myproject/app Environment="PATH=/usr/share/myproject/app/myprojectenv/bin" ExecStart=/usr/share/myproject/app/myprojectenv/bin/gunicorn --workers 3 --bind unix:myproject.sock -m 007 wsgi:application [Install] WantedBy=multi-user.target nginx. Con# For more information on configuration, see: * Official English Documentation: http://nginx.org/en/docs/ * Official Russian Documentation: http://nginx.org/ru/docs/ user nginx; worker_processes 1; error_log /var/log/nginx/error.log; pid /run/nginx.pid; Load dynamic modules. See /usr/share/nginx/README.dynamic. include /usr/share/nginx/modules/*.conf; events { worker_connections 1024; } http { log_format main '$remote_addr - $remote_user [$time_local] "$request" ' '$status $body_bytes_sent "$http_referer" ' '"$http_user_agent" "$http_x_forwarded_for"'; access_log /var/log/nginx/access.log main; sendfile on; tcp_nopush on; tcp_nodelay on; keepalive_timeout 65; types_hash_max_size 2048; include /etc/nginx/mime.types; default_type application/octet-stream; # Load modular configuration files from the /etc/nginx/conf.d directory. # See http://nginx.org/en/docs/ngx_core_module.html#include # for more information. include /etc/nginx/conf.d/*.conf; server { listen 80 default_server; listen [::]:80 default_server; server_name _; root /usr/share/myproject/app; # Load configuration files for the default server block. include /etc/nginx/default.d/*.conf; location / { proxy_pass http://unix:/usr/share/myproject/app/myproject.sock; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } error_page 404 /404.html; location = /40x.html { } error_page 500 502 503 504 /50x.html; location = /50x.html { } } } To build the image: docker build --rm -t cents7-myImage .COnstruct container: docker run -tid -v /sys/fs/cgroup:/sys/fs/cgroup:ro --cap-add SYS_ADMIN -p 8000:80 --name cadprsev centos7-my Image:latest

Good afternoon,Yes, every Docker container runs only one project at a time. In that case, the best would be to create another project and put Docker on it.For each project, a Docker container should be created to use it.Hug.

Yes this is the expected behavior, because vc is overwriting the original command of this image, and the container closes as soon as your command runs.Change your command for the following:command: chown www-data:www-data /var/www/blog/storage && apache2-foreground Original command of this image: https://github.com/docker-library/php/blob/c856411d1c21111855a54c5d29f2bfe099d63ce7/7.1/stretch/apache/Dockerfile#L258

This is not necessarily in relation to Angular, it is more related to network and docker.When you use 127.0.0.1, you are telling your server to listen/serve to the virtual network adapter that meets the internal host, also known as loopback.You need to use 0.0.0.0 so that this server, running within your container, is accessible by all network interfaces. Including external access, in the case of servers, for example.When deploying the application to the host, you need to consider using 0.0.0.0 so that the "redirection" enters the network interface publishes and the network interface of your container, works.If your wish is to leave 0.0.0.0 as default, so you don't need to type, you'll need to set in the angle settings file, something like this: https://stackoverflow.com/a/42788609/6394559

I was able to by configuring the Docker client https://docs.docker.com/network/proxy/#configure-the-docker-client :{ "proxies": { "default": { "httpProxy": "http://10.100.5.107:3128", "noProxy": "*.test.example.com,.example2.com" } } } Follow here, to interested parties, all the steps you need to configure Docker on Ubuntu with the proxy:## Removendo versões antigas sudo apt-get remove docker docker-engine docker.io sudo apt-get update ## Adicionando a chave GPG oficial do Docker curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add - ## Adicionando repo do Docker no APT sudo add-apt-repository \ "deb [arch=amd64] https://download.docker.com/linux/ubuntu \ $(lsb_release -cs) \ stable" sudo apt-get update ## Instala o Docker sudo apt-get install docker-ce ## Executar Docker sem sudo sudo usermod -aG docker $(whoami) ## Configurar proxy sudo mkdir -p /etc/systemd/system/docker.service.d echo "[Service] Environment=\"HTTP_PROXY=http://127.0.0.1:3128\"" > /etc/systemd/system/docker.service.d/http-proxy.conf ## Reunicia o docker pra carregar o proxy sudo systemctl daemon-reload sudo systemctl restart docker Instala o Docker compose sudo curl -L https://github.com/docker/compose/releases/download/1.15.0/docker-compose-uname -s-uname -m -o /usr/local/bin/docker-compose sudo chmod +x /usr/local/bin/docker-compose Adicionar o proxy no docker client mkdir ~/.docker/ echo "{ "proxies": { "default": { "httpProxy": "http://127.0.0.1:3128", "noProxy": "*.test.example.com,.example2.com" } } }" > ~/.docker/config.json

In view of your scenario, I would recommend creating a custom image with the plugin(s) you need, makes it easy instead of running this big command whenever it is start your container.Configuring DockerfileIn the repository https://github.com/grafana/grafana-docker/ has a directory custom/with one Dockerfile to customize, just do the https://github.com/grafana/grafana-docker.git and use.Building the ImageInside the cloned directory (grafana-docker/custom/), build the new image by passing by parameter:the image version of the graphic used as the basis, in the variable GRAFANA_VERSION and the plugins you want to install in the variable GF_INSTALL_PLUGINSSomething like this:docker build -t grafana:atual_com_plugins \ --build-arg "GRAFANA_VERSION=latest" \ --build-arg "GF_INSTALL_PLUGINS=alexanderzobnin-zabbix-app" . Tip1: Instead of using Tag latest always use the latest stable version, in case the version https://hub.docker.com/r/grafana/grafana/ .Initiating containerWith your image successfully built, you can start normally:docker run \ -d \ -p 5200:3000 \ --name=grafana \ -v /docker/grafana/data:/var/lib/grafana \ grafana:atual_com_plugins All this information is available in the documentation http://docs.grafana.org/installation/docker/ .Obs: if it still does not work, make sure that plugin is ok or if it is no problem with the versions of the graphan are no problem.EDIT: As quoted by @beto, if you want to persist data using volume, you need to give permission in the directory where the data will be stored.

Looking calmly, your mistake is identical to an error reported in your comments http://petronetto.com.br/2017/05/08/criando-uma-aplicacao-laravel-com-docker :phpunit/php-code-coverage 6.0.7 requires ext-xmlwriter * -> the requested PHP extension xmlwriter is missing from your system. It's dependencies xmlwriter that was not added to your image.Yours Docker!, add: php7-xmlwriteron the dependency list and do the build of the image again. When running the new image will work properly.

Problem solvedWhen using . env of the laradock MYSQL_VERSION=lasted he used mysql 8.0 and there was a problem. So I changed to 5.7 as follows:docker-compose down Change . env of the laradock... MYSQL_VERSION=5.7 ... Delete the databases: remove all tables from the bank!!rm -rf ~/.laradock/data/mysql Make the builddocker-compose build mysql Go up againdocker-compose up -d apache2 mysql phpmyadmin https://medium.com/@thicolares/como-configurar-um-ambiente-completo-php-nginx-mysql-e-phpmyadmin-para-projetos-laravel-usando-99954285351e