-
Notifications
You must be signed in to change notification settings - Fork 828
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue running make site-server
from build directory
#3885
Comments
It might be because the container is running as root, and the git repo is running as your local user. Does this work if you run the command |
Same issue, I run the repo as a local user and make the site with
|
I hacked in a workaround. I'll post it here soon. Actually it's the exact same as what @Orza posted (see screenshot). Great minds etc etc :) Link to build/includes/website.mk#L32 cc @igooch @markmandel Are you two having issues when running ![]() |
|
Oh cool I wonder what the issue is with @Orza and my dev machines. What dev machine system are you working on? AMD or ARM? I'll try it as is on my intel based MBP later. I'm on my ARM MBP, so I wonder if there's just a difference there... Getting ahead, I wonder if we'll want to modify the generated docker command based on what type of dev machine is running it. |
I'm on x86-64, but the issue is not related to ARM. It is specifically a permissions issue because I'm running Docker with |
if you are on ARM (like an M2) you'll likely run into issues -- I expect a bunch of stuff will break since ARM was not commonplace when this was written. @Orza I never thought of what would happen if people used Docker under I do wonder if the In theory the Yay, supporting different OS's with different architectures and commands 🤦🏻 |
It's fun & an honor to be a part of the bleeding edge. I have an M2 MBP, intel MBP, and Ubuntu thinkpad (amd64). I'll try on all three devices; since this issue represents my M2 MBP I just need to run on other 2 devices. Will report back soon. |
Just confirmed on my x86_64 ubuntu machine that $ lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
Address sizes: 39 bits physical, 48 bits virtual
CPU(s): 8
On-line CPU(s) list: 0-7
Thread(s) per core: 2
Core(s) per socket: 4
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 142
Model name: Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz
Stepping: 12
CPU MHz: 2300.000
CPU max MHz: 4900.0000
CPU min MHz: 400.0000
BogoMIPS: 4599.93
Virtualization: VT-x
L1d cache: 128 KiB
L1i cache: 128 KiB
L2 cache: 1 MiB
L3 cache: 8 MiB
NUMA node0 CPU(s): 0-7
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d arch_capabilities |
I tried removing just
I both removed Looks like making both these changes would help. The PR that introduces |
Created PR with the fix described in above comments here: #3914 |
@igooch what do you think? |
What happened:
I tried setting up a local instance of the agones site locally by following instructions found on agones website to
make site-server
from thebuild
directory. I see that it's ultimately running a hugo server that will bind to port 1313 but from inside a container.I encountered some issues with set up. I tried resolving the issue myself (read more in "what I tried" section) but it was late at night.
Below is log output central to the issue. To highlight a couple things before the output wall:
docker run --privileged --rm tonistiigi/binfmt:qemu-v6.2.0 --install arm64
followed up byinstalling: arm64 cannot register "/usr/bin/qemu-aarch64" to /proc/sys/fs/binfmt_misc/register: write /proc/sys/fs/binfmt_misc/register: no such file or directory
ERROR Failed to read Git log: fatal: detected dubious ownership in repository at '/go/src/agones.dev/agones'
What you expected to happen:
I am able to navigate to
http://localhost:1313
and see a development version of the agones site to validate website changes.How to reproduce it (as minimally and precisely as possible):
cd build make site-server
It seems likely this might be an arm issue, so running arm hardware may also be a prerequisite?
Anything else we need to know?:
Some relevant ARM parts of agones codebase are found here:
I was able to move passed this issue using the following steps.
I set
WITH_ARM64=0
to (air quotes) "resolve" thearm64 cannot register "/usr/bin/qemu-aarch64" to /proc/sys/fs/binfmt_misc/register
issue.I see
git config --global --add safe.directory /go/src/agones.dev/agones
in output so I tried prepending$(git_safe) &&
to build/includes/website.mk#L34 because that makefile variable exactly to that command. I get aPermission denied
error.Permission issue, eh? Next thing is to remove
--user $(UID):$(GID)
from thedocker run
command. This moves me passed the issue and I'm able to see the development website.Environment:
kubectl version
): v1.28.6The text was updated successfully, but these errors were encountered: