Docker Argument '--skip-mac-address' causes rebuild error

Product Support Self-hosting

AI-generated summary

Wolfereign is experiencing an error when rebuilding a Docker container using the --skip-mac-address argument in the container/app.yml configuration file. The error occurs at the beginning of the rebuild process, stating that the flag is unknown and refers to docker run --help. However, when running the command manually with the argument, the rebuild is successful. The goal is to add the argument to the configuration file to avoid having to remember to include it every time a rebuild is necessary.

1

Hi All,

I’m trying to install discourse using docker host networking and am running into a weird error with the rebuild command.

If I run ./launcher rebuild app --docker-args --net=host --skip-mac-address then discourse will rebuild without issue and is accessible from my load balancer.

But if I add the configuration to container/app.yml instead then I get an error at the beginning of the rebuild process.

image
image1162×458 24.4 KB

[root@hpc-discourse-p1 discourse]# ./launcher rebuild app
Device "docker0" does not exist.
x86_64 arch detected.
Ensuring launcher is up to date
Fetching origin
Launcher is up-to-date
unknown flag: --skip-mac-address
See 'docker run --help'.
unknown flag: --skip-mac-address
See 'docker run --help'.
unknown flag: --skip-mac-address
See 'docker run --help'.
unknown flag: --skip-mac-address
See 'docker run --help'.
unknown flag: --skip-mac-address
See 'docker run --help'.
cd /pups && git pull && git checkout v1.0.3 && /pups/bin/pups --stdin
unknown flag: --skip-mac-address
See 'docker run --help'.
cat: cids/app_bootstrap.cid: No such file or directory
"docker rm" requires at least 1 argument.
See 'docker rm --help'.

Usage:  docker rm [OPTIONS] CONTAINER [CONTAINER...]

Remove one or more containers
rm: cannot remove 'cids/app_bootstrap.cid': No such file or directory
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one.
./discourse-doctor may help diagnose the problem.
[root@hpc-discourse-p1 discourse]#

I would like to add this as part of the configuration so that if myself or another admin comes and rebuild, or something similar, we won’t need to remember to add the extra flags every time.