#metabrainz

/

      • supersandro2000 has quit
      • supersandro2000 joined the channel
      • ljunkie has quit
      • ljunkie joined the channel
      • d4rkie has quit
      • D4RK-PH0ENiX joined the channel
      • v6lur_ has quit
      • supersandro2000 has quit
      • supersandro20009 joined the channel
      • Gore has quit
      • Gore joined the channel
      • HenryG has quit
      • HenryG joined the channel
      • Chinmay3199 joined the channel
      • pristine__
        ruaok: yeah, williams. I don't think we have script for hashes and timestamp.
      • KindOne has quit
      • KindOne joined the channel
      • KindTwo joined the channel
      • KindOne has quit
      • KindTwo is now known as KindOne
      • BrainzGit
        [musicbrainz-server] mwiencek opened pull request #1539 (master…types-first): Enable types-first mode in Flow https://github.com/metabrainz/musicbrainz-serve...
      • reosarevok
        bitmap: that one looks fun
      • How much reviewing vs "tests pass, guess it's ok" are you expecting? :p
      • Leftmost
        Got a branch of bookbrainz-site now which is also audit issue-free, but dependent on the -data-js update.
      • Chinmay3199
        I was trying to run again my bb local server using ./develop.sh
      • But I'm getting an error `/bin/bash: /wait: Permission denied`, I used `chmod`to grant it permission but the problem still exists
      • I tried running up the server using `docker-compose up` but that gave me errors:
      • `elasticsearch | /bin/bash: bin/es-docker: Permission denied`
      • `redis | /bin/sh: can't open '/usr/local/bin/docker-entrypoint.sh': Permission denied`
      • `postgres | bash: /usr/local/bin/docker-entrypoint.sh: Permission denied`
      • When I looked into bin folder there wasn't actually any docker-entrypoint.sh file to give permission to. Any suggestions what can I do?
      • BestSteve has quit
      • BestSteve joined the channel
      • Leftmost
        Chinmay3199, I'm not very familiar with docker, but I'm guessing those are permissions issues within the containers, which might suggest something wrong with the docker daemon. Are you on Linux?
      • Chinmay3199
        Yes I'm on linux
      • Leftmost
        I don't have great suggestions, but you could try `docker container prune`, `docker image prune`, and `./develop.sh` again.
      • Chinmay3199
        I already tried that. No success :(
      • Leftmost
        Maybe try a docker support room. Mention that you're running well-maintained containers and each of them is getting "Permission denied" on the ENTRYPOINT.
      • Chinmay3199
        Nice idea. I'll try that!
      • ishaanshah
        iliekcomputers: The tests are done
      • PR is ready for review
      • iliekcomputers
        Great, thanks!
      • Can you open a ticket for the the accessibility eslint disable? It's a code smell and I fear we'll never get to it if we don't fix it soon.
      • yvanzo
        mo’’in’
      • prabal
        Morningg :)
      • shivam-kapila
        Morning
      • ishaanshah
        iliekcomputers: will do, I was thinking that we should use some kind of CSS in JS system moving forward and also upgrade bootstrap to v4
      • shivam-kapila
        Chinmay3199: Hi. Did you add docker to the user group and then reboot your system?
      • Chinmay3199
        Yeah I did that
      • shivam-kapila
        Hm. strange. Maybe Mr_Monkey will be able to help when he is up
      • ishaanshah
        iliekcomputers: the test is failing because of ratelimit on travis
      • Any idea how it can be fixed?
      • BestSteve has quit
      • BestSteve joined the channel
      • diru1100
        Morning!! 🔥🔥 40° C here
      • shivam-kapila
        Was 49° here yesterday
      • iliekcomputers
        ishaanshah: that's very weird
      • We should disable rate limits in tests
      • But it's just the one request, so I'm not sure what's happening
      • Ah, it uses redis
      • In the tearDown method, you could flush redis
      • Search for something like flushdb on livegrep, we should have examples
      • Also, can you open a ticket for disabling rate limits in the test env :D
      • shivam-kapila
      • Flush redis example
      • v6lur_ joined the channel
      • ZaphodBeeblebrox
        heh, it's "only" going to be 22˚C here today (but that's pretty hot for norway in may :x)
      • Mr_Monkey
        Chinmay3199: Well, that's a new error to me. Not sure I have better suggestions than the ones above…
      • iliekcomputers
        this is why people who deny global warming are idiots
      • Mr_Monkey
        Did you try to run the docker commands as sudo, in case that's the issue?
      • iliekcomputers glances sideways at donald trump
      • iliekcomputers
      • alastairp
        Mr_Monkey: that error looks like the script not having +x set
      • note that permission denied happens when you can't read it, but also when you try and run a script without +x set
      • diru1100
        shivam-kapila: damn that's too high 🌡️
      • alastairp
        though yes, there's another question about how it got into that state...
      • Mr_Monkey
        Chinmay3199: Maybe worth checking permissions on your develop.sh file?
      • Mine is -rwxr-xr-x
      • And/or the other sh files in /scripts
      • alastairp
        but the error isn't develop.sh
      • it's inside the container
      • Chinmay3199
        I ran the docker commands as sudo only
      • sumedh joined the channel
      • yvanzo
        do you have bind mounts?
      • Chinmay3199
        I don't know what that is so probable I have don't have them
      • Mr_Monkey
        There are bind mounts (it's when you mount a folder to the container)
      • But the error also appears in containers that have a docker volume and no bind mount
      • Chinmay3199
        Btw I have same -rwxr-xr-x permissions for develop.sh
      • yvanzo
        Maybe try to run bash inside a container to check permissions.
      • alastairp
        Chinmay3199: what happens if you run: `docker-compose run --rm -ti postgres ls -l /usr/local/bin/`
      • yvanzo
        and `docker-compose run --rm -ti postgres whoami`
      • alastairp
        yvanzo: I'm 99% sure that "permission denied" in this case refers to lack of +x, not the owner, but it's worth checking
      • yvanzo
        alastairp: but the same permission issue occurs across all containers, so that might be a more general Docker/Compose issue.
      • Chinmay3199
      • This is what I got on `docker-compose run --rm -ti postgres ls -l /usr/local/bin/`
      • yvanzo
        oops, that's -ti
      • alastairp
        oh yeah, damn. postgres has this entrypoint
      • oh, sorry. it looks like d-c does that already
      • Chinmay3199: remove the `-ti` and try again?
      • Mr_Monkey
        Yeah, this is for a stock postgres image, we don't overwrite the entrypoint at all.
      • Same for redis and elasticsearch
      • alastairp
        -rwxrwxr-x 1 root root 5075 Oct 18 2018 docker-entrypoint.sh
      • Chinmay3199
        `bash: /usr/local/bin/docker-entrypoint.sh: Permission denied`
      • alastairp
        this is what I get for a postgres container that I have
      • Chinmay3199
        Permission error again
      • yvanzo
        Chinmay3199: `docker-compose run --rm postgres whoami`
      • alastairp
        oh yeah, right. all commands go through the entrypoint, and so you can't even run ls
      • yvanzo: that probably won't work either
      • yvanzo
        bash seems to work at least
      • Chinmay3199
        yvanzo: Same error
      • alastairp
        mmm, but that's probably bash of the #! in the entrypoint file
      • ok, `docker run` has an `--entrypoint` argument
      • Mr_Monkey: what's the full name of the postgres container?
      • bookbrainz_postgres ?
      • yvanzo
        Chinmay3199: or `docker-compose run --rm postgres bash` and then type `echo $USER`
      • alastairp
        yvanzo: that won't work
      • Mr_Monkey
        alastairp: postgres
      • alastairp
        because it'll still try and run the entrypoint
      • Mr_Monkey: no, the full name of the container
      • oh, wait
      • mmm
      • yvanzo
        then use the --entrypoint
      • alastairp
        that's not needed
      • right
      • Mr_Monkey
      • alastairp
        bookbrainzsite_postgres, then I think
      • `docker run --rm -ti --entrypoint /bin/bash` postgres
      • uh, the whole command
      • `docker run --rm -ti --entrypoint /bin/bash postgres:12.3`
      • Chinmay3199
        `docker-compose run --rm postgres bash` this didn't run. Permission error
      • Mr_Monkey
        So I think we're barking up the wrong tree and this is an issue with docker rather than with the containers. People on this github issue are suggesting uninstalling Docker they installed with snap, an d reinstalling it with apt.
      • alastairp
        Chinmay3199: do it with 'docker run' and add -ti
      • Mr_Monkey
        Leftmost also had some issues earlier this week and reinstalling from the official package solved it.
      • alastairp
        Mr_Monkey: it seems like an issue with the permissions of the docker overlay directory, but we should at least be able to track down a specific error
      • Chinmay3199: the last command that I pasted should get you a bash shell. does that work for you?
      • Chinmay3199
        `docker run --rm -ti postgres bash` on running this
      • alastairp
        docker run --rm -ti --entrypoint /bin/bash postgres:12.3
      • this one
      • Chinmay3199
        alastairp:
      • `bash: /root/.bashrc: Permission denied`
      • Mr_Monkey
        Chinmay3199: do you use snappy to install packages?
      • Leftmost
        Worth asking which distro and, yeah, install method.
      • alastairp
        wow, that's really strange then. I don't know where to look after this. sorry
      • yvanzo
        alastairp: at least we know it's running as root :)
      • Gazooo has quit
      • Chinmay3199
        Mr_Monkey: No