Paul Colomiets
Paul Colomiets
Currently its: ``` ERROR:vagga::builder: Error building container "ubuntu": step UbuntuRelease { codename: None, version: None, url: Some("https://cloud-images.ubuntu.com/releases/12.04.2/release/ubuntu-12.04-server-cloudimg-amd64.tar.gz"), arch: "amd64", keep_chfn_command: false } failed: Error reading /etc/lsb-release: No such file or...
The common pattern for installing packages is something like this: ``` vagga _build app-freezer cat .vagga/app-freezer/../pip3-freeze.txt > app-requirements.txt vagga _build app ``` Where `app-freezer` contains unversioned dependencies. And `app` contains...
Currently it results into the following error: ``` Can't create namespace file "/run/user/1000/vagga/children/net.172.18.0.1": Permission denied (os error 13) ```
When user have failed to setup `subuid` he receives the error similar to: ``` $ vagga run newuidmap: write to uid_map failed: Invalid argument ERROR:vagga::wrapper: Error executing _build: Can't mount...
It should at least be documented. But probably NixOS should have a module for vagga. First thing that module needs is subuid ranges: ``` subUidRanges = [ { startUid =...
It looks like I have some pattern for the containers, basically for each microservice I have ``` # Fetch latest dependencies, to create requirements.txt app-freezer: setup: ... - !Py3Install [pkga,...
The examples are: 1. Running on vagrant in `/vagrant` folder 2. Same as (1) but running on windows 3. Fuse file systems 4. Some kind of NFS 5. Fat32 or...