How to execute script by host after starting docker container

Question

I have docker-compose.yml file and I start a container with DB via docker-compose up -d db command.

I need to execute script by host machine that, briefly speaking, export dump to db in container.

So, now it looks like:

docker-compose up -d db
./script.sh

But I want to combine these two commands into one. My question is "Is it possible?"

I found out that Docker Compose doesn't support this feature. I know that I can create another script with these commands in it, but I want to leave only docker-compose up -d db

UPD: I would like to mention that I am using mcr.microsoft.com/mssql/server:2017-latest image

Also, have to say one more time that I need to execute script exactly on host machine

This heavily depends on the exact image used. The official postgres docker image, for example, executes all *.sql, *.sql.gz, and *.sh scripts in directory /docker-entrypoint-initdb.d. — Turing85
– Turing85, Commented Mar 20, 2022 at 12:43
@Turing85 Yes, I am going to mention that I am using mcr.microsoft.com/mssql/server:2017-latest image — Никита Петров
– Никита Петров, Commented Mar 20, 2022 at 12:47
This question is similar to: Docker run script in host on docker-compose up. If you believe it’s different, please edit the question, make it clear how it’s different and/or how the answers on that question are not helpful for your problem. — MarkR
– MarkR, Commented Oct 9, 2024 at 15:19

David Maze · Accepted Answer · 2022-03-20 13:08:15Z

4

You can't use the Docker tools to execute commands on the host system. A general design point around Docker is that containers shouldn't be able to affect the host.

Nothing stops you from writing your own shell script that runs on the host and does the steps you need:

#!/bin/sh
docker-compose -d up
./wait-for.sh localhost 1433
./script.sh

(The wait-for.sh script is the same as described in the answers to Docker Compose wait for container X before starting Y that don't depend on Docker health checks.)

For your use case it may be possible to run the data importer in a separate container. A typical setup could look like this; note that the importer will run every time you run docker-compose up. You may want to actually build this into a separate image.

version: '3.8'
services:
  db: { same: as you have currently }
  importer:
    image: mcr.microsoft.com/mssql/server:2017-latest
    entrypoint: ./wait-for.sh db 1433 -- ./script.sh
    workdir: /import
    volumes: [.:/import]

The open-source database containers also generally support putting scripts in /docker-entrypoint-initdb.d that get executed the first time the container is launched, but the SQL Server image doesn't seem to support this; questions like How can I restore an SQL Server database when starting the Docker container? have a complicated setup to replicate this behavior.

answered Mar 20, 2022 at 13:08

David Maze

165k47 gold badges262 silver badges301 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Никита Петров Over a year ago

Thanks a lot! Probably, the way of using another container is appropriate for me!

Collectives™ on Stack Overflow

How to execute script by host after starting docker container

1 Answer 1

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related