Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Paul Colomiets
    @tailhook
    Hi everyone! I've started a contest for logo on 99 designs. Here is the issue to subscribe for updates: tailhook/vagga#491 Also, feel free to discuss it here.
    Paul Colomiets
    @tailhook
    Here is the first, preliminary poll for logo: https://99designs.com/contests/poll/3bf78334c0
    It will helps us give more guidance to designers, it's not for the final logo.
    Matthias Vegh
    @matthiasvegh
    Hi! I'm trying to run Thunderbird within vagga, and so far everything works, except opening links. As there is no browser inside the container, Thunderbird doesn't know how to open the link. I was hoping that xdg-open would just work with the X11 socket mounted, but doesn't. Do you have any suggestions? I'm considering writing an xdg-open proxy, that would communicate with the host via unix domain socket to issue the xdg-open in the host namespace instead of the container, but that seems like a hack.
    Paul Colomiets
    @tailhook
    Hi! Everything that wants to "escape" the container probably requires the hack you described. Some things may communicate via X11 socket (I certainly know gvim does that, but I'm not sure about firefox/chrome). But to make that work you need the same browser executable in the container too. xdg-open just calls the command as far as I know, it doesn't communicate to the browser by itself.
    Matthias Vegh
    @matthiasvegh
    Right, I was thinking of putting a custom xdg-open binary into the container that would call out to the host.
    Paul Colomiets
    @tailhook
    We have a poll for the final logo, please, take a look: https://99designs.com/contests/poll/71fabfbf5e
    Kon Tsaki
    @laerus
    cool!
    Kon Tsaki
    @laerus
    hey firefox doesn't like the certificates for https://vagga.rtfd.org/
    vagga.rtfd.org uses an invalid security certificate.
    The certificate is only valid for the following names: *.readthedocs.org, readthedocs.org 
    Error code: SSL_ERROR_BAD_CERT_DOMAIN
    Paul Colomiets
    @tailhook
    @laerus, you should report this bug to readthedocs.org.
    Kon Tsaki
    @laerus
    oh right
    Paul Colomiets
    @tailhook
    In the meantime we can change the link, if it's hanging somewhere...
    Kon Tsaki
    @laerus
    seems like an old issue rtfd/readthedocs.org#3059 :(
    Karel Wintersky
    @KarelWintersky
    Hi, All. How to compile Vagga at gentoo using rust docker container?
    error: environment variable `VAGGA_VERSION` not defined
      --> src/config/config.rs:56:26
    fails here.
    (можно отвечать на русском ;) )
    Karel Wintersky
    @KarelWintersky
    Solved.
    docker run --rm --user "$(id -u)":"$(id -g)" -e VAGGA_VERSION=v0.8.1-19-g372bded -v "$PWD":/usr/src/myapp -w /usr/src/myapp rust cargo build --release
    Lloyd Konneker
    @bootchk
    • !Sh 'git clone --recurse-submodules git://github.com/flathub/org.gimp.GIMP' seems to create a directory org.gimp.GIMP at the top i.e. in parent directory of vagga.yaml, i.e. not in the container. That seems bad. I suppose I can do the recursion myself.
    Paul Colomiets
    @tailhook
    @bootchk, I've already answered on a github, but basically, just cd into a specific directory in the container (we don't forbid mutating working directory, as it would crash a lot of tools out of the box)
    Michael Pankov
    @mkpankov
    hey, from the docs I got the impression that I can build a container with vagga and run it with docker.
    is it correct? how do I do it?
    Paul Colomiets
    @tailhook
    @mkpankov, yes. You should be able to do something like vagga _pack_image CONTAINER_NAME > image.tar; docker import image.tar (or ADD image.tar / in Dockerfile)
    Michael Pankov
    @mkpankov
    thanks, not a docker user so it was really a riddle
    Michael Pankov
    @mkpankov
    hey
    I have several repos where I want to use vagga, currently I've put vagga.yaml in first one. now I've discovered I need to share parts of vagga.yaml between repos (i.e. definition of Rust container). how should I do that?
    I've read about YAML includes and mixins, I can't quite put it together. both of them are restricted to including stuff from sub-directories. why?
    Paul Colomiets
    @tailhook
    @mkpankov, this is a a security measure. So that when you run vagga xxx from a foreign project it can't stole your ssh keys or similar. You can share configs either but putting them in git submodule (and updating manually), or you can mount --bind a subdirectory into several places. Or you can use external-volumes to overcome that limiation (although, it would require configuring them for every user).
    Michael Pankov
    @mkpankov
    thanks for quick reply. to me that seems like a lot of overhead for something I'd like to have out-of-the-box. I mean, submodules are hell and mounting something manually when the purpose of vagga is to avoid doing that... what is your opinion on something that could be built-in?
    or, maybe I should just write a "root" vagga.yaml and move everything there? so that project repos don't contain one and come just as source repositories
    context is, I have repos of two rust tools, one of which runs the other, so they are almost always used together
    Paul Colomiets
    @tailhook
    Technically you can, if you like it.
    I usually install one tool in the second's vagga.yaml as a normal package (e.g. cargo install)
    And then if I want debug something very coupled I use mount --bind or just copy thing in ad hoc way.
    Alternatively, you can also make a command which fetches mixin remotely before the first start.
    Michael Pankov
    @mkpankov
    my tools are proprietary and we currently don't run our registry, so I can't cargo install
    I guess I'd like something of "best practice" advice (even better if it's in the docs)

    Alternatively, you can also make a command which fetches mixin remotely before the first start.

    that's interesting

    that way I can share my include/mixin w/o access to parent directory, could work, I think
    btw, are symlinks followed? If I ln -s ../include.yaml include.yaml?
    Paul Colomiets
    @tailhook
    No, that would kill whole security :)
    Michael Pankov
    @mkpankov
    yeah, thought so)
    Paul Colomiets
    @tailhook

    I'd like something of "best practice" advice

    I usually recommend as independent repos as possible, i.e. that you can vagga run in any one. And use git submodules for thing that can't be fetched from package repos. The big advantage of submodules that you can always mount --bind on top. Not sure it's anywhere in the docs.

    Michael Pankov
    @mkpankov
    what do you mean by "mount --bind on top"? like, why would I need it
    (sorry if it's stupid question, I'm a novice with containers)
    Paul Colomiets
    @tailhook
    I.e you have ./proj1 and ./proj2. And also ./proj1/proj2 is a git submodule. Sometimes you edited ./proj2 and want to try it inside ./proj1: cd proj1; mount --bind ../proj2 proj2 and you have it.
    https://medium.com/@paulcolomiets/announcing-vagga-0-7-1-85b9a9e84f2a
    Section "mixins" describes how to "generate" mixin (in your case 'generating' might be just fetching somewhere)
    Michael Pankov
    @mkpankov
    thanks, will try that
    Michael Pankov
    @mkpankov
    a side question: are you actively developing vagga currently?
    Paul Colomiets
    @tailhook
    @mkpankov, I don't have time recently, so we definitely have some technical debt (i.e. need to release a stable). But this is a thing that I'm using every day more that any other command-line tool (for obvious reasons :) ). And there are other people like me (hard to count). So I don't consider project abandoned. And I'm looking forward to spent more time on it.
    Michael Pankov
    @mkpankov
    hey. in case you have advices on how to debug this, I'd appreciate it
    tailhook/vagga#519
    Paul Colomiets
    @tailhook
    @mkpankov Answered in github issue. Hopefully, that is helpful