Closed kikitux closed 9 years ago
Are you useing Downloading or copying: file:///Volumes/hd1/Dropbox/work/packer-vagrant/fedora-atomic-packer/boot.iso
instead of OVF?
I guess that is a problem.
deleted and running again..
I am running a copy of the project on github as is.. no changes
will report back soon
z2-3:fedora-atomic-packer kikitux$ rm boot.iso
z2-3:fedora-atomic-packer kikitux$ make | tee make.log
curl -LO http://rpm-ostree.cloud.fedoraproject.org/project-atomic/install/rawhide/20140708.0/boot.iso
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left
Speed
25 750M 25 193M 0 0 22.9M 0 0:00:32 0:00:08 0:00:24 26.2M
On Sun, Oct 19, 2014 at 5:42 PM, YungSang notifications@github.com wrote:
Are you useing Downloading or copying: file:///Volumes/hd1/Dropbox/work/packer-vagrant/fedora-atomic-packer/boot.iso instead of OVF? I guess that is a problem.
— Reply to this email directly or view it on GitHub https://github.com/YungSang/fedora-atomic-packer/issues/7#issuecomment-59639167 .
Oh are you trying to build from scratch instal of upgrade?
from scratch install, for some reason is not working for me.
did a new git clone, failed.
deleted the boot.iso and i am trying again..
On Sun, Oct 19, 2014 at 5:45 PM, YungSang notifications@github.com wrote:
Oh are you trying to build from scratch instal of upgrade?
— Reply to this email directly or view it on GitHub https://github.com/YungSang/fedora-atomic-packer/issues/7#issuecomment-59639230 .
Strange... Do you see the boot command in a VirtualBox GUI window?
the machine boots install. run the commands,, with those warnings.. reboot i see the gui… it fail to shutdown.
gui is left running, i can login as vagrant/vagrant but sudo fail with same warning..
perhaps once the box is created something did change on atomic repo ???
On 19/10/2014, at 5:50 pm, YungSang notifications@github.com wrote:
Strange... Do you see the boot command in a VirtualBox GUI window?
— Reply to this email directly or view it on GitHub.
i see the gui… it fail to shutdown.
This is a problem. After installation is complete, the boot config will set sudo setting. see http/atomic-ks.cfg
I experience a sudo problem as well in the latest installation. Umm...
ithink something changed upstream
On Sun, Oct 19, 2014 at 6:06 PM, YungSang notifications@github.com wrote:
I experience a sudo problem as well in the latest installation. Umm...
— Reply to this email directly or view it on GitHub https://github.com/YungSang/fedora-atomic-packer/issues/7#issuecomment-59639525 .
Yup.
Anyway, I have created the upgraded box and tested it. It is over 100 MB bigger than the original box...
any faster than pulling all from internet?
Yes, it's much faster. Thank you so much for your idea.
When the sudo problem is fixed, I will release it.
can you push to a dev branch?
On Sun, Oct 19, 2014 at 7:04 PM, YungSang notifications@github.com wrote:
Yes, it's much faster. Thank you so much for your idea.
When the sudo problem is fixed, I will release it.
— Reply to this email directly or view it on GitHub https://github.com/YungSang/fedora-atomic-packer/issues/7#issuecomment-59640530 .
ok, seems i found the issue.. there is a hidden ^M character in http/atomic-ks.cfg
on the line cat << EOF > /etc/sudoers.d/vagrant^M
did you edit on windows? I am on OSX.
so the file gets created like that on the linux vm
I did login as root/vagrant did an ls and saw the issue.
Oh really? I'm on OSX. I will check it.
yeah, got pass that part immediately :+1: :smile:
I don't see any hidden character in it...
i did dos2unix and rertry and work.. the base box build finally
command i run: dos2unix http/atomic-ks.cfg
after that.. ==> Builds finished. The artifacts of successful builds are: --> virtualbox: VM files in directory: output-virtualbox --> virtualbox: 'virtualbox' provider box: ../fedora-atomic-virtualbox.box z2-3:fedora-atomic-packer kikitux$
Umm.. It is not a dos format on my local OSX.
BTW, how long does it take to build it from scratch on your side?
In my case, systemd-hostnamed
in the latest one has something wrong.
sudo hostnamectl set-hostname something.domain.name
fails.
i am running it again. did make clean, now I am running as
time make | tee make.log
so will capture time and will check logs.. i didn't notice some commands fail.
will check logs once it finish
On Sun, Oct 19, 2014 at 8:36 PM, YungSang notifications@github.com wrote:
In my case, systemd-hostnamed in the latest one has something wrong. sudo hostnamectl set-hostname something.domain.name fails.
— Reply to this email directly or view it on GitHub https://github.com/YungSang/fedora-atomic-packer/issues/7#issuecomment-59642097 .
@kikitux Thank you so much for your help.
all good.. I did really like the way you used make here to build the system, and how you have make test.
I can see the value..
I have a lot of machines that I build, and reuse, and I am using shell scripts at the moment, but make is way more cooler and better.. will try to see what I can get
On Sun, Oct 19, 2014 at 8:41 PM, YungSang notifications@github.com wrote:
@kikitux https://github.com/kikitux Thank you so much for your help.
— Reply to this email directly or view it on GitHub https://github.com/YungSang/fedora-atomic-packer/issues/7#issuecomment-59642202 .
Because I don't have a good network here, so it is too slow to build it... over 2 hours...
Thanks a lot.
My wifi connection has something wrong currently. I will check it again later.
Time, this is a mac mini in usa.
real 14m26.198s
user 0m35.223s
sys 0m10.166s
Did update the gist with the outputs of make upo and make test
https://gist.github.com/kikitux/d37b67c6a8dd1a76656e
On Sun, Oct 19, 2014 at 8:43 PM, alvaro miranda kikitux@gmail.com wrote:
as for network, same here.. I am in New Zealand.. pretty bad international internet.
But I do have a mac mini hosted on macminivault with a very fast pipe, so I ssh there and use that machine to build my boxes.
On 19/10/2014, at 8:43 pm, YungSang notifications@github.com wrote:
Because I don't have a good network here, so it is too slow to build it... over 2 hours...
— Reply to this email directly or view it on GitHub https://github.com/YungSang/fedora-atomic-packer/issues/7#issuecomment-59642253 .
That log looks good. Thanks again.
For some reason my make run fail
any hint?
https://gist.github.com/kikitux/d37b67c6a8dd1a76656e