vagga
vagga copied to clipboard
tailhook
Vagga is a containerization tool without daemons
change version of alpine package where older version no longer be available will fix one of my build issues from #577
```bash vagga --mount-bind $HOME/.cargo:/work/target/.cargo run ``` At the moment we can emulate such a behavior: `vagga.yaml`: ```yaml commands: run-ci: !Command
Implemented: - Build step options: `registry`, `image`, `tag`, `path`, `insecure` - Short form: `!DockerImage python`, `!DockerImage python:3.10-slim` - Insecure registries - Registries that don't support authentication - Cache layers; wait...
Have a PoC of the `!DockerImage` build step: ```yaml containers: python: setup: - !DockerImage image: library/python version: 3.10-slim ``` What do you think about it? TODO: - [x] Build step...
The crashed process: ``` ERROR:vagga::builder: Error building container "py": step Install(["ca-certificates", "python3.6=3.6.2-1~16.04.york0"]) failed: error running killed by signal SIGBUS[7] ``` The waiting process: ``` Get:15 http://ua.archive.ubuntu.com xenial-security/restricted Translation-en [2428 B]...
i have been facing busybox issue every time when i downloaded from the external source. latesti downloaded [busybox pro](https://apkadda.com/busybox-pro-apk/) from their and also working fine but after sometime facing issue....
Is it possible to use / run existing docker images or do they always have to be built separately using vagga?
I am trying to define a vagga build gile which must perform a checkout from a private git repository. Authentication happens, as usual, with ssh keys. The problem is that...
Hi, I need help with an issue I'm encountering consistently on my project. I couldn't minimize it yet - maybe you can tell what's wrong already. This issue occurs when...
Replacing env!("VAGGA_VERSION") to env!("CARGO_PKG_VERSION") make possibility use vagga as library
