Coder Social home page Coder Social logo

docker-inotify's People

Contributors

pstauffer avatar

Stargazers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Watchers

avatar avatar avatar

Forkers

elcweb mediakraken-dependancies cinadr kquinsland yangchuansheng killbus echobar findawaytofreedom yongman smcdonald45 lodemo kroschu sonroyaalmerol

docker-inotify's Issues

Error in `exclude' regular expression.

I meet error:

$ docker-compose up inotify
Pulling inotify (pstauffer/inotify:v1.0.1)...
v1.0.1: Pulling from pstauffer/inotify
Creating dnmp_inotify_1 ... done
Attaching to dnmp_inotify_1
inotify_1        \| Error in `exclude' regular expression.
inotify_1        \| inotify settings
inotify_1        \| ================
inotify_1        \|
inotify_1        \|   Container:        php72
inotify_1        \|   Volumes:          /data
inotify_1        \|   Curl_Options:
inotify_1        \|   Signal:           SIGHUP
inotify_1        \|   Inotify_Events:   create,delete,modify,move
inotify_1        \|   Inotify_Options:  --monitor --exclude=*.sw[px]
inotify_1        \|
inotify_1        \| [Starting inotifywait...]
dnmp_inotify_1 exited with code 0

My docker-compose.yml file is:

  inotify:
    image: pstauffer/inotify:v1.0.1
    tty: "true"
    volumes:
      - ${SOURCE_DIR}/theme/themefile/:/data:rw
      - /var/run/docker.sock:/var/run/docker.sock:ro
    environment:
      - CONTAINER=php72
      - VOLUMES=/data

Not working; unsure why

I'm using docker-inotify along with your bind nameserver to reload my zone file when it changes.

The zone file is in a directory from the host mapped into the volume with compose, e.g.,

    volumes:
    - ./data/foo:/etc/bind/foo

But when I touch data/foo/bar.zone (for example), there's no notification event fired. Nothing in the logs, no SIGHUP, nothing.

I'm not really sure where to proceed from here. Is it that inotify doesn't work with volumes mounted from the host?

Requests to docker daemon fail after curl update

It seems that curl 7.5x changed how URLs were handled for unix sockets, which prevents the kill request used in init.sh from succeeding (the docker daemon responds instead with a 404).

There's some discussion around the change at moby/moby#17960 (comment), but briefly in older versions of curl http:/containers/xyz resulted in a request for /containers/xyz, and in newer versions it results in a Host: containers header and a request for /xyz

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.