8
molaram
53d

fucking docker
fucking compose

fucking linux

why can't this shit ever fucking work properly? without any motherfucking drama and timewaste?

Step 7/9 : ADD _scripts/setup_postgres_readonly_user.sh /tmp/setup_postgres_readonly_user.sh
---> 5a8cc407913b
Step 8/9 : ADD run.sh /run.sh
---> db2b76e84849

[...]

setup_databases | /run.sh: line 6: /tmp/setup_postgres_readonly_user.sh: not found

fucking waste of 3 hours I could have done ANYTHING ELSE but stare at this shit trying to figure out why the fuck these things just won't work as they're supposed to.

Comments
  • 3
    How is it the fault of docker, compose or Linux, if you’re script is fucked?

    That’s like blaming your ide, the language and your OS, if your code won’t compile or has a bug
  • 0
    @dontknowshit well not necessarily docker or linux themselves but more like the lack of clarity in those fucking errors and the way a whole fucking stack can crash over some small thing.

    In this particular case someone set a script to run under /bin/bash and when switched to alpine it was supposed to use /bin/sh. Yet it was hard to guess what the fuck was happening as the error seems like the whole fucking script was missing.

    Bottom line is 3 hours wasted which could have been saved if the fucking error would say "at line 1 in your-fucking-script.sh: /bin/bash not found" or something along these lines.
  • 0
    But you know that if you rerun the build, only the last step is repeated?

    And not found is imo pretty clear.
  • 1
    @nitwhiz ran it like 15 times before figuring out /bin/bash was missing, not that shit script.

    maybe i just need to learn how to read errors. this isn't what i usually do but my devops guy is mia so guess who has to do the whole fucking thing by himself.
  • 0
    ohh..poor boy.....It seems you are totally fucked up.
  • 1
    @molaram Nah, it's just that Linux shell doesn't have descriptive errors. Best you can do is learn what to check if you get this error, like script permissions, line endings, hashbangs, ...
  • 1
    @dontknowshit you dontknowshit

    Sorry I couldnt help myself...
  • 0
    @zemaitis technically he does have a point, it wasn't exactly docker's fault. but all this crap thrown together can be rather counterintuitive so docker can suck it up as well.

    how hard can it be to write something like "looks like you're rebuilding this image 3rd time today, type this shit <cmd> to clear the cache too!"

    sometimes i feel these tools were not made for humans to work with.

    don't get me wrong, docker is great, but it could be so much better. and if you're gonna say "It'S oPeN SoUrcE mAtE, go ahead and improve it" then good luck getting a PR looked at...
  • 1
    @molaram people who start sentences with "technically, obviously, actually" scare me
  • 1
    @zemaitis I'll try to remember to start with "maybe" or "perhaps" or something similar :)
  • 1
    @zemaitis Even sentence starts with "ideally" also.
  • 0
    Rule of thumb: always assume a docker image has absolutely nothing except for /bin/sh unless you explicitly installed it.
  • 0
    @molaram how did you end up with the conclusion that bash was missing? The error message said that it cannot find the script from step 6 which is added to the /tmp directory, which in turn is deleted in step 7 because it is a new container.

    I know it is almost a month ago, but still I got curious.
  • 1
    @TheCommoner282 after setting the shebang to /bin/sh it worked
Add Comment