Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Bug Report: [docker] - container won't start due to missing build files #14344

Closed
FirePing32 opened this issue Oct 23, 2023 · 0 comments · Fixed by #14363
Closed

Bug Report: [docker] - container won't start due to missing build files #14344

FirePing32 opened this issue Oct 23, 2023 · 0 comments · Fixed by #14363
Labels
Component: Docker Type: Bug

Comments

@FirePing32
Copy link
Contributor

Overview of the Issue

The docker image created by make docker_local does not generate build files for vtadmin-web, and causes 101_initial_cluster.sh to fail. Also, the Dockerfile exits with the bash command due to which the container stops when detaching from the shell.

Also see: #13454

Reproduction Steps

make docker_local
make docker_run_local

Binary Version

vtgate version Version: 19.0.0-SNAPSHOT (Git revision 64d7eb6838e14a4d296a3a3ab47b33412716b4e0 branch 'remove-deps') built on Mon Oct 23 15:04:57 UTC 2023 by prakhar@ubuntu using go1.21.3 linux/amd64

Operating System and Environment details

PRETTY_NAME="Ubuntu 22.04.3 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.3 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy

Kernel - Linux 5.15.0-87-generic
Arch - x86_64

Log Fragments

Starting etcd...
add zone1 CellInfo
ERROR: logging before flag.Parse: E1023 20:27:18.100653      33 syslogger.go:149] can't connect to syslog
W1023 20:27:18.177200      33 vtctl.go:124] cannot connect to syslog: Unix syslog delivery error
Created cell: zone1
etcd is running!
Starting vtctld...
vtctld is running!
ERROR: logging before flag.Parse: E1023 20:27:18.864174      75 syslogger.go:149] can't connect to syslog
Successfully created keyspace commerce. Result:
{
  "name": "commerce",
  "keyspace": {
    "served_froms": [],
    "keyspace_type": "NORMAL",
    "base_keyspace": "",
    "snapshot_time": null,
    "durability_policy": "semi_sync",
    "throttler_config": null,
    "sidecar_db_name": "_vt"
  }
}
Starting MySQL for tablet zone1-0000000102...
Starting MySQL for tablet zone1-0000000100...
Starting MySQL for tablet zone1-0000000101...
ERROR: logging before flag.Parse: E1023 20:27:19.051869     102 syslogger.go:149] can't connect to syslog
ERROR: logging before flag.Parse: E1023 20:27:19.052216     105 syslogger.go:149] can't connect to syslog
ERROR: logging before flag.Parse: E1023 20:27:19.052293     106 syslogger.go:149] can't connect to syslog
Waiting for mysqlctls to start...
MySQL for tablet zone1-0000000102 is running!
MySQL for tablet zone1-0000000101 is running!
MySQL for tablet zone1-0000000100 is running!
mysqlctls are running!
Starting vttablet for zone1-0000000100...
HTTP/1.1 200 OK
Date: Mon, 23 Oct 2023 20:27:28 GMT
Content-Type: text/html; charset=utf-8

vttablet for zone1-0000000100 is running!
Starting vttablet for zone1-0000000101...
HTTP/1.1 200 OK
Date: Mon, 23 Oct 2023 20:27:28 GMT
Content-Type: text/html; charset=utf-8

vttablet for zone1-0000000101 is running!
Starting vttablet for zone1-0000000102...
HTTP/1.1 200 OK
Date: Mon, 23 Oct 2023 20:27:28 GMT
Content-Type: text/html; charset=utf-8

vttablet for zone1-0000000102 is running!
Starting vtorc...
vtorc is running!
  - UI: http://localhost:16000
  - Logs: /vt/vtdataroot/tmp/vtorc.out
  - PID: 1940

ERROR: logging before flag.Parse: E1023 20:27:28.534235    1943 syslogger.go:149] can't connect to syslog
ERROR: logging before flag.Parse: E1023 20:27:28.671211    1955 syslogger.go:149] can't connect to syslog
ERROR: logging before flag.Parse: E1023 20:27:28.739541    1967 syslogger.go:149] can't connect to syslog
ERROR: logging before flag.Parse: E1023 20:27:29.790197    1977 syslogger.go:149] can't connect to syslog
ERROR: logging before flag.Parse: E1023 20:27:30.828534    1988 syslogger.go:149] can't connect to syslog
ERROR: logging before flag.Parse: E1023 20:27:31.873458    1997 syslogger.go:149] can't connect to syslog
ERROR: logging before flag.Parse: E1023 20:27:32.913275    2007 syslogger.go:149] can't connect to syslog
ERROR: logging before flag.Parse: E1023 20:27:33.948220    2017 syslogger.go:149] can't connect to syslog
ERROR: logging before flag.Parse: E1023 20:27:34.982021    2027 syslogger.go:149] can't connect to syslog
ERROR: logging before flag.Parse: E1023 20:27:36.016770    2036 syslogger.go:149] can't connect to syslog
ERROR: logging before flag.Parse: E1023 20:27:37.052282    2046 syslogger.go:149] can't connect to syslog
ERROR: logging before flag.Parse: E1023 20:27:38.099108    2056 syslogger.go:149] can't connect to syslog
ERROR: logging before flag.Parse: E1023 20:27:39.135153    2066 syslogger.go:149] can't connect to syslog
ERROR: logging before flag.Parse: E1023 20:27:40.171136    2076 syslogger.go:149] can't connect to syslog
ERROR: logging before flag.Parse: E1023 20:27:41.206234    2086 syslogger.go:149] can't connect to syslog
ERROR: logging before flag.Parse: E1023 20:27:42.241612    2096 syslogger.go:149] can't connect to syslog
ERROR: logging before flag.Parse: E1023 20:27:43.275436    2106 syslogger.go:149] can't connect to syslog
ERROR: logging before flag.Parse: E1023 20:27:44.309421    2159 syslogger.go:149] can't connect to syslog
ERROR: logging before flag.Parse: E1023 20:27:45.385204    2186 syslogger.go:149] can't connect to syslog
ERROR: logging before flag.Parse: E1023 20:27:45.435782    2200 syslogger.go:149] can't connect to syslog
ERROR: logging before flag.Parse: E1023 20:27:45.478466    2210 syslogger.go:149] can't connect to syslog
ERROR: logging before flag.Parse: E1023 20:27:45.533299    2220 syslogger.go:149] can't connect to syslog
ERROR: logging before flag.Parse: E1023 20:27:45.628934    2235 syslogger.go:149] can't connect to syslog
ERROR: logging before flag.Parse: E1023 20:27:46.894092    2283 syslogger.go:149] can't connect to syslog

ERROR: logging before flag.Parse: E1023 20:27:47.168603    2295 syslogger.go:149] can't connect to syslog
New VSchema object:
{
  "sharded": false,
  "vindexes": {},
  "tables": {
    "corder": {
      "type": "",
      "column_vindexes": [],
      "auto_increment": null,
      "columns": [],
      "pinned": "",
      "column_list_authoritative": false,
      "source": ""
    },
    "customer": {
      "type": "",
      "column_vindexes": [],
      "auto_increment": null,
      "columns": [],
      "pinned": "",
      "column_list_authoritative": false,
      "source": ""
    },
    "product": {
      "type": "",
      "column_vindexes": [],
      "auto_increment": null,
      "columns": [],
      "pinned": "",
      "column_list_authoritative": false,
      "source": ""
    }
  },
  "require_explicit_routing": false,
  "foreign_key_mode": "FK_DEFAULT"
}
If this is not what you expected, check the input data (as JSON parsing will skip unexpected fields).
Starting vtgate...
vtgate is up!
Access vtgate at http://6819f9ae5452:15001/debug/status
vtadmin-api is running!
  - API: http://6819f9ae5452:14200
  - Logs: /vt/vtdataroot/tmp/vtadmin-api.out
  - PID: 2350

ERROR: Please make sure the VTAdmin files are built in ../common/scripts/../../../web/vtadmin/build, using 'make build'
make: *** [Makefile:351: docker_run_local] Error 1
@FirePing32 FirePing32 added Needs Triage This issue needs to be correctly labelled and triaged Type: Bug labels Oct 23, 2023
@FirePing32 FirePing32 mentioned this issue Oct 25, 2023
Merged
4 tasks
@frouioui frouioui added Component: Docker and removed Needs Triage This issue needs to be correctly labelled and triaged labels Oct 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Component: Docker Type: Bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Docker] Fix VTadmin build FirePing32/vitess
2 participants
@frouioui @FirePing32