rlenferink commented on PR #656: URL: https://github.com/apache/celix/pull/656#issuecomment-1752110539
> What's the advantage of using container over using a Vagrant box (virtual machine)? > > In my personal experience, containers have far more restrictions than VM, and is generally more difficult to set up correctly. Most of the issues discussed here don't exist if VMs are used, and we won't have #658. Yes, containers are more efficient than VMs, but that does not mean much except for CI. Moreover, Vagrant can work with [containers](https://developer.hashicorp.com/vagrant/docs/provisioning/podman). > > For individual developer, Vagrant can serve as a convenient CLI, whether using VMs or containers. For me personally it is that I am familiar with containers and am using them extensively, and am not familiar / have never used vagrant. My experience with VMs is that it is quite often just a bit slower and file-sharing between host and VM is mostly a pain point (how else do we get to use an IDE ?). > I cannot yet build the image, getting the following error: > > > Setting up python3.10-minimal (3.10.12-1~22.04.2) ... > > [Errno 13] Permission denied: '/usr/lib/python3.10/**pycache**/**future**.cpython-310.pyc.140478821390960'dpkg: error processing package python3.10-minimal (--configure): > > installed python3.10-minimal package post-installation script subprocess returned error exit status 1 > > Errors were encountered while processing: > > python3.10-minimal > > E: Sub-process /usr/bin/dpkg returned an error code (1) > > The command '/bin/sh -c DEBIAN_FRONTEND="noninteractive" apt-get update && DEBIAN_FRONTEND="noninteractive" apt-get install -y --no-install-recommends dos2unix git locales-all rsync tar ssh tzdata build-essential ccache cmake curl default-jdk gcc g++ gdb make python3 civetweb libavahi-compat-libdnssd-dev libcivetweb-dev libcpputest-dev libcurl4-openssl-dev libczmq-dev libffi-dev libjansson-dev libxml2-dev libzip-dev rapidjson-dev uuid-dev && apt-get clean' returned a non-zero code: 100 Just for reference, the command I used was `cd container && podman build -t apache/celix-dev:2.4.0-ubuntu -f Containerfile.ubuntu .` (as non-root user) and the OS I am using is Fedora 38. I removed all my cached images and it still builds; so I am not sure what is going wrong here. What OS are you using? > This is also why I am not sure if we should add a dev container or dev virtual machine configuration, this requires us to maintain and document the dev container image and/or virtual machine configuration. This indeed is true. Whether we offer a dev container, a VM template or something else, it needs to be maintained. > The reason why I see more value in a gitpod config or Github codespaces is that this enable users / potential developers to try out Apache Celix without setting up a machine or even needing a machine (browser based). So they could start coding with a minimal hassle. But also for gitpod / codespaces we should consider how much effort it is going to be to maintain the gitpod/codespaces configuration. For me personally I am not extremely content with more-and-more usage of cloud-based technology for these kind of things. The main reason is that only the first 'X' amount of hours is for free and if a certain amount of hours is exceeded then there is a need to pay said providers (obviously). Since I am mostly using my personal environment for this and doing this outside of work I have no intend to pay for these services. I am definitely not against having a codespaces/gitpod image, but at least there should be an alternative so we don't force people to use these providers if they don't want to (or there should be instructions on how to use it locally). Maybe we should/could even be offering multiple developer solutions (vanilla container, codespaces container, VM template etc...) ? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@celix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
