Incompatible with CoreOS

[tribou]

I'm receiving the following error when attempting to apply proxy settings to a CoreOS VM:

mv: inter-device move failed: '/tmp/vagrant-proxyconf' to '/etc/profile.d/proxy.sh'; unable to remove target: Read-only file system

Manually adding HTTP_PROXY and HTTPS_PROXY variables do not appear to work with CoreOS either.

[tmatilai]

@artribou thanks for the report! I haven't played with CoreOS yet at all, so I have to study a bit. But it seems that /etc is mounted read-only. Do you have a link to a CoreOS box or AMI that I could use for testing?

[tribou]

Yep, here's the box I was using: https://github.com/coreos/coreos-vagrant

[tmatilai]

@artribou what should vagrant-procysonf do with CoreOS? The whole root partition is read-only and not supposed to be modified.
What are you doing on the VM and how it should be configured to use a proxy server? Do you have an example project (Vagrantfile with provisioners)?

I can disable vagrant-proxyconf env var writing in CoreOS but currently I have no idea if we can do something else. =)

[tribou]

I understand. I've been fighting with it for a week now and knew it was a long-shot request anyway.

From behind a proxy, I'm not able to use any of the "docker pull", "docker search", etc. commands to download new docker images to the CoreOS VM. This is more likely to be an issue that should be resolved on the CoreOS or Docker side.

[tmatilai]

This is probably related: moby/moby#1852

[tmatilai]

So I just disabled writing the environment variables on CoreOS. Let's revisit the situation when Docker supports proxies. Or if someone has other ideas.