[atomic-wg] Issue #181 `Vagrant cannot create synced folder`
by Pagure
jorti reported a new issue against the project: `atomic-wg` that you are following:
``
I just launch an unmodified fedora/25-atomic-host box and I get the error that it cannot create the /vagrant synced dir.
```
$ vagrant up
Bringing machine 'default' up with 'libvirt' provider...
==> default: Creating image (snapshot of base box volume).
==> default: Creating domain with the following settings...
==> default: -- Name: mail-server_default
==> default: -- Domain type: kvm
==> default: -- Cpus: 1
==> default: -- Memory: 512M
==> default: -- Management MAC:
==> default: -- Loader:
==> default: -- Base box: fedora/25-atomic-host
==> default: -- Storage pool: default
==> default: -- Image:
/var/lib/libvirt/images/mail-server_default.img (41G)
==> default: -- Volume Cache: default
==> default: -- Kernel:
==> default: -- Initrd:
==> default: -- Graphics Type: vnc
==> default: -- Graphics Port: 5900
==> default: -- Graphics IP: 127.0.0.1
==> default: -- Graphics Password: Not defined
==> default: -- Video Type: cirrus
==> default: -- Video VRAM: 9216
==> default: -- Keymap: en-us
==> default: -- TPM Path:
==> default: -- INPUT: type=mouse, bus=ps2
==> default: -- Command line :
==> default: Creating shared folders metadata...
==> default: Starting domain.
==> default: Waiting for domain to get an IP address...
==> default: Waiting for SSH to become available...
default:
default: Vagrant insecure key detected. Vagrant will automatically replace
default: this with a newly generated keypair for better security.
default:
default: Inserting generated public key within guest...
default: Removing insecure key from the guest if it's present...
default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Configuring and enabling network interfaces...
==> default: Rsyncing folder: /home/juan/Vagrant/mail-server/ => /vagrant
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
mkdir -p /vagrant
Stdout from the command:
Stderr from the command:
mkdir: cannot create directory ‘/vagrant’: Operation not permitted
```
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/181
6 years, 10 months
next steps for migrating Cloud Base image to Fedora Server?
by Matthew Miller
I think we had general agreement around what we want to do here:
have the Cloud Base Image become instead Fedora Server, but shipped
as a cloud image and made available in cloud providers. What are the
next steps to actually get there?
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
7 years, 2 months
[atomic-wg] Issue #185 `November 21 ISO is not bootable`
by Pagure
jberkus reported a new issue against the project: `atomic-wg` that you are following:
``
I'm currently testing the November 21 ISOs by installing on my minnowboard cluster. It seems to be the case that these ISOs are not bootable; after getting through most of the install, they give the following error:
failed to write boot loader configration
Once the new ISOs are available, we need to retest and see if this is a general issue.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/185
7 years, 2 months
Proposal: require DESCRIPTION, USAGE label for images
by Josh Berkus
Folks,
Looking at the new FDLIBS, I'm noticing that there's not a narrative
description of the image required or provided anywhere that I can find.
Clearly one is needed for users. So, here's a proposal:
New Required LABELs:
USAGE: single command line giving usage example
for invoking the container; will be "N/A" for
some containers.
DESCRIPTION: Narrative description incuding:
* What service/software it provides
* What specific purpose it fulfills, if required
* Notes on how to use it, if not covered by USAGE,
such as how to supply configuration files
* Depedencies on other images (e.g. "requires a database")
* Links to documentation for the Software, if any
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
7 years, 3 months
patch for mariadb image
by Casper
Hi everybody,
As I can see, the automated build on the official registry
(hub.dokcer.com) is in failure since few months. I tried to reproduce
it and I think I found a solution.
Here is the patch, not very complex. Merry Chrismas Fedoristas!
--- Dockerfile.old 2016-12-25 19:28:04.307064692 +0100
+++ Dockerfile.new 2016-12-25 19:28:51.489582337 +0100
@@ -32,7 +32,7 @@ RUN INSTALL_PKGS="rsync tar gettext host
rpm -V $INSTALL_PKGS && \
dnf clean all && \
mkdir -p /var/lib/mysql/data && chown -R mysql.0 /var/lib/mysql && \
- rpm -q --qf '%{version}' mariadb-server | grep -e '10\.0\.' && \
+ rpm -q --qf '%{version}' mariadb-server | grep -e '10\.1\.' && \
test "$(id mysql)" = "uid=27(mysql) gid=27(mysql) groups=27(mysql)"
# Get prefix path and path to scripts rather than hard-code them in scripts
--
GPG Key ID: 83288189 @ hkp://keys.fedoraproject.org
Empreinte: CC26 692F 5205 AC8F 7912 7783 D7A7 F4C5 8328 8189
x509 C.A.: https://dl.casperlefantom.net/pub/root.pem
Empreinte: 0975 864A 2036 0F94 A139 114A D32E 8EBE 30F2 2429
7 years, 3 months